Method for tracking area update in wireless communication system and apparatus therefor

ABSTRACT

Disclosed herein are a method for tracking area update in a wireless communication system and an apparatus therefor. Specifically, a method for user equipment (UE) to perform a tracking area update (TAU) procedure in a wireless communication system comprises: a step of transmitting a TAU request message to a mobility management entity (MME); and a step of receiving a TAU accept message from the MME, wherein if the UE uses signaling optimization to enable the delivery of user data through a control plane over the MME, and the UE does not have pending user data to be transmitted through a user plane and has pending user data to be transmitted through the control plane over the MME, then a first active flag can be set in the TAU request message.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is the National Stage filing under 35 U.S.C. 371 ofInternational Application No. PCT/KR2017/003157, filed on Mar. 23, 2017,which claims the benefit of U.S. Provisional Application No. 62/311,927,filed on Mar. 23, 2016, 62/313,109, filed on Mar. 24, 2016, 62/320,665,filed on Apr. 11, 2016, 62/325,985, filed on Apr. 21, 2016, 62/331,453,filed on May 4, 2016, and 62/333,820, filed on May 9, 2016, the contentsof which are all hereby incorporated by reference herein in theirentireties.

TECHNICAL FIELD

The present invention relates to a wireless communication system, andmore particularly, to a method for performing or supporting a trackingupdate procedure and an apparatus for supporting the same.

BACKGROUND ART

Mobile communication systems have been developed to provide voiceservices, while guaranteeing user activity. Service coverage of mobilecommunication systems, however, has extended even to data services, aswell as voice services, and currently, an explosive increase in traffichas resulted in shortage of resource and user demand for a high speedservices, requiring advanced mobile communication systems.

The requirements of the next-generation mobile communication system mayinclude supporting huge data traffic, a remarkable increase in thetransfer rate of each user, the accommodation of a significantlyincreased number of connection devices, very low end-to-end latency, andhigh energy efficiency. To this end, various techniques, such as smallcell enhancement, dual connectivity, massive Multiple Input MultipleOutput (MIMO), in-band full duplex, non-orthogonal multiple access(NOMA), supporting super-wide band, and device networking, have beenresearched.

DISCLOSURE Technical Problem

An embodiment of the present invention provides a method for trackingarea update for efficient data transmission in a case where a UE hasdata to be transmitted when the UE starts a tracking area updateprocedure.

Furthermore, an embodiment of the present invention provides a methodfor maintaining a signaling connection between the UE and an MME afterthe tracking area update procedure when a previous state of the UE issuspension.

It will be appreciated by persons skilled in the art that the objectsthat could be achieved with the present invention are not limited towhat has been particularly described hereinabove and the above and otherobjects that the present invention could achieve will be more clearlyunderstood from the following detailed description.

Technical Solution

In an aspect of the present invention, a method for performing, by auser equipment (UE), a tracking area update (TAU) procedure in awireless communication system includes: transmitting a TAU requestmessage to a mobility management entity (MME); and receiving a TAUaccept message from the MME, in which when the UE uses signalingoptimization to enable the delivery of user data through a control planevia the MME, and the UE does not have pending user data to betransmitted through a user plane and has pending user data to betransmitted through the control plane via the MME, then a first activeflag may be set in the TAU request message.

Preferably, the first active flag may indicate a request for maintaininga non-access stratum (NAS) signaling connection between the UE and theMME after completion of the TAU procedure.

Preferably, the first active flag may be included in an additionalupdate type information element for providing additional informationregarding a type of a request for the TAU procedure in the TAU requestmessage.

Preferably, when a value of the first active flag is ‘0’, the non-accessstratum (NAS) signaling connection between the UE and the MME may not bemaintained after the completion of the TAU procedure.

Preferably, when a value of the first active flag is ‘1’, the non-accessstratum (NAS) signaling connection between the UE and the MME may bemaintained after the completion of the TAU procedure.

Preferably, the method may further include determining whether to drivea predetermined timer according to whether the first active flag in theTAU request message is set when the TAU accept message is received.

Preferably, when the first active flag in the TAU request message is notset, the timer starts and when the timer expires, the non-access stratum(NAS) signaling connection between the UE and the MME may be released bythe UE.

Preferably, in a case where the UE does not successfully perform the TAUprocedure and a mobility management (MM) back-off timer is driven, theTAU request may be transmitted when the UE receives a paging.

Preferably, when the UE has the pending user data through the userplane, a second active flag may be set in the TAU request message.

In another aspect of the present invention, a method for performing, bya mobility management entity (MME), a tracking area update (TAU)procedure in a wireless communication system includes: receiving a TAUrequest message from a user equipment (UE); and transmitting a TAUaccept message from the UE, in which when a first active flag is set inthe TAU request message, a non-access stratum (NAS) signaling connectionbetween the UE and the MME may not be released after completion of theTAU procedure, and the first active flag may indicate a request formaintaining the non-access stratum (NAS) signaling connection betweenthe UE and the MME after the completion of the TAU procedure.

Preferably, when the first active flag is not set in the TAU request,the non-access stratum (NAS) signaling connection may be released.

Preferably, first active flag may be included in an additional updatetype information element for providing additional information regardinga type of a request for the TAU procedure in the TAU request message.

Preferably, when a value of the first active flag is ‘0’, the non-accessstratum (NAS) signaling connection between the UE and the MME may not bemaintained after the completion of the TAU procedure.

Preferably, when a value of the first active flag is ‘1’, the non-accessstratum (NAS) signaling connection between the UE and the MME may bemaintained after the completion of the TAU procedure.

Advantageous Effects

According to an embodiment of the present invention, a UE which usescontrol plane cellular Internet of things (CIoT) evolved packet system(EPS) optimization may efficiently transmit user data via a controlplane after a tracking area update is completed.

Furthermore, according to an embodiment of the present invention, a UEwhich uses user plane CIoT EPS optimization may efficiently transmit theuser data via a user plane after the tracking area update is completed.

It will be appreciated by persons skilled in the art that the effectsthat can be achieved with the present invention are not limited to whathas been particularly described hereinabove and other advantages of thepresent invention will be more clearly understood from the followingdetailed description.

DESCRIPTION OF DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the present invention and constitute a part ofspecifications of the present invention, illustrate embodiments of thepresent invention and together with the corresponding descriptions serveto explain the principles of the present invention.

FIG. 1 is a diagram schematically exemplifying an evolved packet system(EPS) to which the present invention can be applied.

FIG. 2 illustrates an example of evolved universal terrestrial radioaccess network structure to which the present invention can be applied.

FIG. 3 exemplifies a structure of E-UTRAN and EPC in a wirelesscommunication system to which the present invention can be applied.

FIG. 4 illustrates a structure of a radio interface protocol between aUE and E-UTRAN in a wireless communication system to which the presentinvention can be applied.

FIG. 5 is a diagram schematically showing a structure of a physicalchannel in a wireless communication system to which the presentinvention may be applied.

FIG. 6 is a diagram for describing a contention based random accessprocedure in a wireless communication system to which the presentinvention may be applied.

FIG. 7 is a diagram illustrating a MTC (Machine-Type Communication)architecture in a wireless communication system to which the presentinvention may be applied.

FIG. 8 a diagram illustrating an architecture for service capabilityexposure in a wireless communication system to which the presentinvention may be applied.

FIG. 9 illustrates a legacy RRC connection procedure in a wirelesscommunication system to which the present invention may be applied.

FIG. 10 is a diagram illustrating an end to end small data flow in awireless communication system to which the present invention may beapplied.

FIG. 11 is a diagram illustrating CP CIoT EPS optimization and UP CIoTEPS optimization for mobile originated data in a wireless communicationsystem to which the present invention may be applied.

FIG. 12 is a diagram illustrating CP CIoT EPS optimization and UP CIoTEPS optimization for mobile terminated data in a wireless communicationsystem to which the present invention may be applied.

FIG. 13 is a diagram illustrating a release assistanceindication/information information element in a wireless communicationsystem to which the present invention may be applied.

FIG. 14 illustrates a tracking area update procedure in a wirelesscommunication system to which the present invention may be applied.

FIG. 15 illustrates a tracking area update procedure in a wirelesscommunication system to which the present invention may be applied.

FIG. 16 illustrates a tracking area update procedure in a wirelesscommunication system to which the present invention may be applied.

FIG. 17 illustrates a tracking area update procedure in a wirelesscommunication system to which the present invention may be applied.

FIG. 18 is a diagram illustrating an S1 release procedure in a wirelesscommunication system to which the present invention may be applied.

FIG. 19 is a diagram illustrating control plane optimization and userplane optimization in a wireless communication system to which thepresent invention may be applied.

FIG. 20 illustrates a tracking area update procedure according to anembodiment of the present invention.

FIG. 21 illustrates a tracking area update procedure according to anembodiment of the present invention.

FIG. 22 is a diagram illustrating an additional update type informationelement according to an embodiment of the present invention.

FIG. 23 is a diagram illustrating an EPS update type information elementaccording to an embodiment of the present invention.

FIG. 24 is a diagram illustrating a new indication information elementfor connection release according to an embodiment of the presentinvention.

FIG. 25 illustrates a block diagram of a communication apparatusaccording to an embodiment of the present invention.

FIG. 26 illustrates a block diagram of a wireless communicationapparatus according to an embodiment of the present invention.

MODE FOR INVENTION

In what follows, preferred embodiments according to the presentinvention will be described in detail with reference to appendeddrawings. The detailed descriptions provided below together withappended drawings are intended only to explain illustrative embodimentsof the present invention, which should not be regarded as the soleembodiments of the present invention. The detailed descriptions belowinclude specific information to provide complete understanding of thepresent invention. However, those skilled in the art will be able tocomprehend that the present invention can be embodied without thespecific information.

For some cases, to avoid obscuring the technical principles of thepresent invention, structures and devices well-known to the public canbe omitted or can be illustrated in the form of block diagrams utilizingfundamental functions of the structures and the devices.

A base station in this document is regarded as a terminal node of anetwork, which performs communication directly with a UE. In thisdocument, particular operations regarded to be performed by the basestation may be performed by an upper node of the base station dependingon situations. In other words, it is apparent that in a networkconsisting of a plurality of network nodes including a base station,various operations performed for communication with a UE can beperformed by the base station or by network nodes other than the basestation. The term Base Station (BS) can be replaced with a fixedstation, Node B, evolved-NodeB (eNB), Base Transceiver System (BTS), orAccess Point (AP). Also, a terminal can be fixed or mobile; and the termcan be replaced with User Equipment (UE), Mobile Station (MS), UserTerminal (UT), Mobile Subscriber Station (MSS), Subscriber Station (SS),Advanced Mobile Station (AMS), Wireless Terminal (WT), Machine-TypeCommunication (MTC) device, Machine-to-Machine (M2M) device, orDevice-to-Device (D2D) device.

In what follows, downlink (DL) refers to communication from a basestation to a terminal, while uplink (UL) refers to communication from aterminal to a base station. In downlink transmission, a transmitter canbe part of the base station, and a receiver can be part of the terminal.Similarly, in uplink transmission, a transmitter can be part of theterminal, and a receiver can be part of the base station.

Specific terms used in the following descriptions are introduced to helpunderstanding the present invention, and the specific terms can be usedin different ways as long as it does not leave the technical scope ofthe present invention.

The technology described below can be used for various types of wirelessaccess systems based on Code Division Multiple Access (CDMA), FrequencyDivision Multiple Access (FDMA), Time Division Multiple Access (TDMA),Orthogonal Frequency Division Multiple Access (OFDMA), Single CarrierFrequency Division Multiple Access (SC-FDMA), or Non-Orthogonal MultipleAccess (NOMA). CDMA can be implemented by such radio technology asUniversal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can beimplemented by such radio technology as Global System for Mobilecommunications (GSM), General Packet Radio Service (GPRS), or EnhancedData rates for GSM Evolution (EDGE). OFDMA can be implemented by suchradio technology as the IEEE 802.11 (Wi-Fi), the IEEE 802.16 (WiMAX),the IEEE 802-20, or Evolved UTRA (E-UTRA). UTRA is part of the UniversalMobile Telecommunications System (UMTS). The 3rd Generation PartnershipProject (3GPP) Long Term Evolution (LTE) is part of the Evolved UMTS(E-UMTS) which uses the E-UTRA, employing OFDMA for downlink and SC-FDMAfor uplink transmission. The LTE-A (Advanced) is an evolved version ofthe 3GPP LTE system.

Embodiments of the present invention can be supported by standarddocuments disclosed in at least one of wireless access systems includingthe IEEE 802, 3GPP, and 3GPP2 specifications. In other words, among theembodiments of the present invention, those steps or parts omitted forthe purpose of clearly describing technical principles of the presentinvention can be supported by the documents above. Also, all of theterms disclosed in this document can be explained with reference to thestandard documents.

To clarify the descriptions, this document is based on the 3GPPLTE/LTE-A, but the technical features of the present invention are notlimited to the current descriptions.

Terms used in this document are defined as follows.

-   -   Universal Mobile Telecommunication System (UMTS): the 3rd        generation mobile communication technology based on GSM,        developed by the 3GPP    -   Evolved Packet System (EPS): a network system comprising an        Evolved Packet Core (EPC), a packet switched core network based        on the Internet Protocol (IP) and an access network such as the        LTE and UTRAN. The EPS is a network evolved from the UMTS.    -   NodeB: the base station of the UMTS network. NodeB is installed        outside and provides coverage of a macro cell.    -   eNodeB: the base station of the EPS network. eNodeB is installed        outside and provides coverage of a macro cell.    -   User Equipment (UE): A UE can be called a terminal, Mobile        Equipment (ME), or Mobile Station (MS). A UE can be a portable        device such as a notebook computer, mobile phone, Personal        Digital Assistant (PDA), smart phone, or a multimedia device; or        a fixed device such as a Personal Computer (PC) or        vehicle-mounted device. The term UE may refer to an MTC terminal        in the description related to MTC.    -   IP Multimedia Subsystem (IMS): a sub-system providing multimedia        services based on the IP    -   International Mobile Subscriber Identity (IMSI): a globally        unique subscriber identifier assigned in a mobile communication        network    -   Machine Type Communication (MTC): communication performed by        machines without human intervention. It may be called        Machine-to-Machine (M2M) communication.    -   MTC terminal (MTC UE or MTC device): a terminal (for example, a        vending machine, meter, and so on) equipped with a communication        function operating through a mobile communication network (For        example, communicating with an MTC server via a PLMN) and        performing an MTC function    -   MTC server: a server on a network managing MTC terminals. It can        be installed inside or outside a mobile communication network.        It can provide an interface through which an MTC user can access        the server. Also, an MTC server can provide MTC-related services        to other servers (in the form of Services Capability Server        (SCS)) or the MTC server itself can be an MTC Application        Server.    -   (MTC) application: services (to which MTC is applied) (for        example, remote metering, traffic movement tracking, weather        observation sensors, and so on)    -   (MTC) Application Server: a server on a network in which (MTC)        applications are performed    -   MTC feature: a function of a network to support MTC        applications. For example, MTC monitoring is a feature intended        to prepare for loss of a device in an MTC application such as        remote metering, and low mobility is a feature intended for an        MTC application with respect to an MTC terminal such as a        vending machine.    -   MTC User (MTC User): The MTC user uses the service provided by        the MTC server.    -   MTC subscriber: an entity having a connection relationship with        a network operator and providing services to one or more MTC        terminals.    -   MTC group: an MTC group shares at least one or more MTC features        and denotes a group of MTC terminals belonging to MTC        subscribers.    -   Services Capability Server (SCS): an entity being connected to        the 3GPP network and used for communicating with an MTC        InterWorking Function (MTC-IWF) on a Home PLMN (HPLMN) and an        MTC terminal. The SCS provides the capability for use by one or        more MTC applications.    -   External identifier: a globally unique identifier used by an        external entity (for example, an SCS or an Application Server)        of the 3GPP network to indicate (or identify) an MTC terminal        (or a subscriber to which the MTC terminal belongs). An external        identifier comprises a domain identifier and a local identifier        as described below.    -   Domain identifier: an identifier used for identifying a domain        in the control region of a mobile communication network service        provider. A service provider can use a separate domain        identifier for each service to provide an access to a different        service.    -   Local identifier: an identifier used for deriving or obtaining        an International Mobile Subscriber Identity (IMSI). A local        identifier should be unique within an application domain and is        managed by a mobile communication network service provider.    -   Radio Access Network (RAN): a unit including a Node B, a Radio        Network Controller (RNC) controlling the Node B, and an eNodeB        in the 3GPP network. The RAN is defined at the terminal level        and provides a connection to a core network.    -   Home Location Register (HLR)/Home Subscriber Server (HSS): a        database provisioning subscriber information within the 3GPP        network. An HSS can perform functions of configuration storage,        identity management, user state storage, and so on.    -   RAN Application Part (RANAP): an interface between the RAN and a        node in charge of controlling a core network (in other words, a        Mobility Management Entity (MME)/Serving GPRS (General Packet        Radio Service) Supporting Node (SGSN)/Mobile Switching Center        (MSC)).    -   Public Land Mobile Network (PLMN): a network formed to provide        mobile communication services to individuals. The PLMN can be        formed separately for each operator.    -   Non-Access Stratum (NAS): a functional layer for exchanging        signals and traffic messages between a terminal and a core        network at the UMTS and EPS protocol stack. The NAS is used        primarily for supporting mobility of a terminal and a session        management procedure for establishing and maintaining an IP        connection between the terminal and a PDN GW.    -   Service Capability Exposure Function (SCEF): An entity within        the 3GPP architecture for service capability exposure that        provides a means for securely exposing services and capabilities        provided by 3GPP network interfaces.

In what follows, the present invention will be described based on theterms defined above.

Overview of System to which the Present Invention May be Applied

FIG. 1 illustrates an Evolved Packet System (EPS) to which the presentinvention can be applied.

The network structure of FIG. 1 is a simplified diagram restructuredfrom an Evolved Packet System (EPS) including Evolved Packet Core (EPC).

The EPC is a main component of the System Architecture Evolution (SAE)intended for improving performance of the 3GPP technologies. SAE is aresearch project for determining a network structure supporting mobilitybetween multiple heterogeneous networks. For example, SAE is intended toprovide an optimized packet-based system which supports various IP-basedwireless access technologies, provides much more improved datatransmission capability, and so on.

More specifically, the EPC is the core network of an IP-based mobilecommunication system for the 3GPP LTE system and capable of supportingpacket-based real-time and non-real time services. In the existingmobile communication systems (namely, in the 2nd or 3rd mobilecommunication system), functions of the core network have beenimplemented through two separate sub-domains: a Circuit-Switched (CS)sub-domain for voice and a Packet-Switched (PS) sub-domain for data.However, in the 3GPP LTE system, an evolution from the 3rd mobilecommunication system, the CS and PS sub-domains have been unified into asingle IP domain. In other words, in the 3GPP LTE system, connectionbetween UEs having IP capabilities can be established through anIP-based base station (for example, eNodeB), EPC, and application domain(for example, IMS). In other words, the EPC provides the architectureessential for implementing end-to-end IP services.

The EPC comprises various components, where FIG. 1 illustrates part ofthe EPC components, including a Serving Gateway (SGW or S-GW), PacketData Network Gateway (PDN GW or PGW or P-GW), Mobility Management Entity(MME), Serving GPRS Supporting Node (SGSN), and enhanced Packet DataGateway (ePDG).

The SGW operates as a boundary point between the Radio Access Network(RAN) and the core network and maintains a data path between the eNodeBand the PDN GW. Also, in case the UE moves across serving areas by theeNodeB, the SGW acts as an anchor point for local mobility. In otherwords, packets can be routed through the SGW to ensure mobility withinthe E-UTRAN (Evolved-UMTS (Universal Mobile Telecommunications System)Terrestrial Radio Access Network defined for the subsequent versions ofthe 3GPP release 8). Also, the SGW may act as an anchor point formobility between the E-UTRAN and other 3GPP networks (the RAN definedbefore the 3GPP release 8, for example, UTRAN or GERAN (GSM (GlobalSystem for Mobile Communication)/EDGE (Enhanced Data rates for GlobalEvolution) Radio Access Network).

The PDN GW corresponds to a termination point of a data interface to apacket data network. The PDN GW can support policy enforcement features,packet filtering, charging support, and so on. Also, the PDN GW can actas an anchor point for mobility management between the 3GPP network andnon-3GPP networks (for example, an unreliable network such as theInterworking Wireless Local Area Network (I-WLAN) or reliable networkssuch as the Code Division Multiple Access (CDMA) network and WiMax).

In the example of a network structure as shown in FIG. 1, the SGW andthe PDN GW are treated as separate gateways; however, the two gatewayscan be implemented according to single gateway configuration option.

The MME performs signaling for the UE's access to the network,supporting allocation, tracking, paging, roaming, handover of networkresources, and so on; and control functions. The MME controls controlplane functions related to subscribers and session management. The MMEmanages a plurality of eNodeBs and performs signaling of theconventional gateway's selection for handover to other 2G/3G networks.Also, the MME performs such functions as security procedures,terminal-to-network session handling, idle terminal location management,and so on.

The SGSN deals with all kinds of packet data including the packet datafor mobility management and authentication of the user with respect toother 3GPP networks (for example, the GPRS network).

The ePDG acts as a security node with respect to an unreliable, non-3GPPnetwork (for example, I-WLAN, WiFi hotspot, and so on).

As described with respect to FIG. 1, a UE with the IP capability canaccess the IP service network (for example, the IMS) that a serviceprovider (namely, an operator) provides, via various components withinthe EPC based not only on the 3GPP access but also on the non-3GPPaccess.

Also, FIG. 1 illustrates various reference points (for example, S1-U,S1-MME, and so on). The 3GPP system defines a reference point as aconceptual link which connects two functions defined in disparatefunctional entities of the E-UTAN and the EPC. Table 1 below summarizesreference points shown in FIG. 1. In addition to the examples of FIG. 1,various other reference points can be defined according to networkstructures.

TABLE 1 Reference point Description S1-MME Reference point for thecontrol plane protocol between E-UTRAN and MME S1-U Reference pointbetween E-UTRAN and Serving GW for the per bearer user plane tunnelingand inter eNodeB path switching during handover S3 It enables user andbearer information exchange for inter 3GPP access network mobility inidle and/or active state. This reference point can be used intra-PLMN orinter-PLMN (e.g. in the case of Inter-PLMN HO). S4 It provides relatedcontrol and mobility support between GPRS core and the 3GPP anchorfunction of Serving GW. In addition, if direct tunnel is notestablished, it provides the user plane tunneling. S5 It provides userplane tunneling and tunnel management between Serving GW and PDN GW. Itis used for Serving GW relocation due to UE mobility if the Serving GWneeds to connect to a non-collocated PDN GW for the required PDNconnectivity. S11 Reference point for the control plane protocol betweenMME and SGW SGi It is the reference point between the PDN GW and thepacket data network. Packet data network may be an operator externalpublic or private packet data network or an intra-operator packet datanetwork (e.g., for provision of IMS services). This reference pointcorresponds to Gi for 3GPP accesses.

Among the reference points shown in FIG. 1, S2a and S2b corresponds tonon-3GPP interfaces. S2a is a reference point which provides reliable,non-3GPP access, related control between PDN GWs, and mobility resourcesto the user plane. S2b is a reference point which provides relatedcontrol and mobility resources to the user plane between ePDG and PDNGW.

FIG. 2 illustrates one example of an Evolved Universal Terrestrial RadioAccess Network (E-UTRAN) to which the present invention can be applied.

The E-UTRAN system is an evolved version of the existing UTRAN system,for example, and is also referred to as 3GPP LTE/LTE-A system.Communication network is widely deployed in order to provide variouscommunication services such as voice (e.g., Voice over Internet Protocol(VoIP)) through IMS and packet data.

Referring to FIG. 2, E-UMTS network includes E-UTRAN, EPC and one ormore UEs. The E-UTRAN includes eNBs that provide control plane and userplane protocol, and the eNBs are interconnected with each other by meansof the X2 interface.

The X2 user plane interface (X2-U) is defined among the eNBs. The X2-Uinterface provides non-guaranteed delivery of the user plane Packet DataUnit (PDU). The X2 control plane interface (X2-CP) is defined betweentwo neighboring eNBs. The X2-CP performs the functions of contextdelivery between eNBs, control of user plane tunnel between a source eNBand a target eNB, delivery of handover-related messages, uplink loadmanagement, and so on.

The eNB is connected to the UE through a radio interface and isconnected to the Evolved Packet Core (EPC) through the S1 interface.

The S user plane interface (S1-U) is defined between the eNB and theServing Gateway (S-GW). The S1 control plane interface (S1-MME) isdefined between the eNB and the Mobility Management Entity (MME). The S1interface performs the functions of EPS bearer service management,non-access stratum (NAS) signaling transport, network sharing, MME loadbalancing management, and so on. The S1 interface supportsmany-to-many-relation between the eNB and the MME/S-GW.

The MME may perform various functions such as NAS signaling security,Access Stratum (AS) security control, Core Network (CN) inter-nodesignaling for supporting mobility between 3GPP access network, IDLE modeUE reachability (including performing paging retransmission andcontrol), Tracking Area Identity (TAI) management (for UEs in idle andactive mode), selecting PDN GW and SGW, selecting MME for handover ofwhich the MME is changed, selecting SGSN for handover to 2G or 3G 3GPPaccess network, roaming, authentication, bearer management functionincluding dedicated bearer establishment, Public Warning System (PWS)(including Earthquake and Tsunami Warning System (ETWS) and CommercialMobile Alert System (CMAS), supporting message transmission and so on.

FIG. 3 exemplifies a structure of E-UTRAN and EPC in a wirelesscommunication system to which the present invention can be applied.

Referring to FIG. 3, an eNB may perform functions of selecting gateway(e.g., MME), routing to gateway during radio resource control (RRC) isactivated, scheduling and transmitting broadcast channel (BCH), dynamicresource allocation to UE in uplink and downlink, mobility controlconnection in LTE_ACTIVE state. As described above, the gateway in EPCmay perform functions of paging origination, LTE_IDLE state management,ciphering of user plane, bearer control of System Architecture Evolution(SAE), ciphering of NAS signaling and integrity protection.

FIG. 4 illustrates a radio interface protocol structure between a UE andan E-UTRAN in a wireless communication system to which the presentinvention can be applied.

FIG. 4(a) illustrates a radio protocol structure for the control plane,and FIG. 4(b) illustrates a radio protocol structure for the user plane.

With reference to FIG. 4, layers of the radio interface protocol betweenthe UE and the E-UTRAN can be divided into a first layer (L), a secondlayer (L2), and a third layer (L3) based on the lower three layers ofthe Open System Interconnection (OSI) model, widely known in thetechnical field of communication systems. The radio interface protocolbetween the UE and the E-UTRAN consists of the physical layer, data linklayer, and network layer in the horizontal direction, while in thevertical direction, the radio interface protocol consists of the userplane, which is a protocol stack for delivery of data information, andthe control plane, which is a protocol stack for delivery of controlsignals.

The control plane acts as a path through which control messages used forthe UE and the network to manage calls are transmitted. The user planerefers to the path through which the data generated in the applicationlayer, for example, voice data, Internet packet data, and so on aretransmitted. In what follows, described will be each layer of thecontrol and the user plane of the radio protocol.

The physical layer (PHY), which is the first layer (L), providesinformation transfer service to upper layers by using a physicalchannel. The physical layer is connected to the Medium Access Control(MAC) layer located at the upper level through a transport channelthrough which data are transmitted between the MAC layer and thephysical layer. Transport channels are classified according to how andwith which features data are transmitted through the radio interface.And data are transmitted through the physical channel between differentphysical layers and between the physical layer of a transmitter and thephysical layer of a receiver. The physical layer is modulated accordingto the Orthogonal Frequency Division Multiplexing (OFDM) scheme andemploys time and frequency as radio resources.

A few physical control channels are used in the physical layer. ThePhysical Downlink Control Channel (PDCCH) informs the UE of resourceallocation of the Paging Channel (PCH) and the Downlink Shared Channel(DL-SCH); and Hybrid Automatic Repeat reQuest (HARQ) information relatedto the Uplink Shared Channel (UL-SCH). Also, the PDCCH can carry a ULgrant used for informing the UE of resource allocation of uplinktransmission. The Physical Control Format Indicator Channel (PCFICH)informs the UE of the number of OFDM symbols used by PDCCHs and istransmitted at each subframe. The Physical HARQ Indicator Channel(PHICH) carries a HARQ ACK (ACKnowledge)/NACK (Non-ACKnowledge) signalin response to uplink transmission. The Physical Uplink Control Channel(PUCCH) carries uplink control information such as HARQ ACK/NACK withrespect to downlink transmission, scheduling request, Channel QualityIndicator (CQI), and so on. The Physical Uplink Shared Channel (PUSCH)carries the UL-SCH.

The MAC layer of the second layer (L2) provides a service to the RadioLink Control (RLC) layer, which is an upper layer thereof, through alogical channel. Also, the MAC layer provides a function of mappingbetween a logical channel and a transport channel; andmultiplexing/demultiplexing a MAC Service Data Unit (SDU) belonging tothe logical channel to the transport block, which is provided to aphysical channel on the transport channel.

The RLC layer of the second layer (L2) supports reliable datatransmission. The function of the RLC layer includes concatenation,segmentation, reassembly of the RLC SDU, and so on. To satisfy varyingQuality of Service (QoS) requested by a Radio Bearer (RB), the RLC layerprovides three operation modes: Transparent Mode (TM), UnacknowledgedMode (UM), and Acknowledge Mode (AM). The AM RLC provides errorcorrection through Automatic Repeat reQuest (ARQ). Meanwhile, in casethe MAC layer performs the RLC function, the RLC layer can beincorporated into the MAC layer as a functional block.

The Packet Data Convergence Protocol (PDCP) layer of the second layer(L2) performs the function of delivering, header compression, cipheringof user data in the user plane, and so on. Header compression refers tothe function of reducing the size of the Internet Protocol (IP) packetheader which is relatively large and contains unnecessary control toefficiently transmit IP packets such as the IPv4 (Internet Protocolversion 4) or IPv6 (Internet Protocol version 6) packets through a radiointerface with narrow bandwidth. The function of the PDCP layer in thecontrol plane includes delivering control plane data andciphering/integrity protection.

The Radio Resource Control (RRC) layer in the lowest part of the thirdlayer (L3) is defined only in the control plane. The RRC layer performsthe role of controlling radio resources between the UE and the network.To this purpose, the UE and the network exchange RRC messages throughthe RRC layer. The RRC layer controls a logical channel, transportchannel, and physical channel with respect to configuration,reconfiguration, and release of radio bearers. A radio bearer refers toa logical path that the second layer (L2) provides for data transmissionbetween the UE and the network. Configuring a radio bearer indicatesthat characteristics of a radio protocol layer and channel are definedto provide specific services; and each individual parameter andoperating methods thereof are determined. Radio bearers can be dividedinto Signaling Radio Bearers (SRBs) and Data RBs (DRBs). An SRB is usedas a path for transmitting an RRC message in the control plane, while aDRB is used as a path for transmitting user data in the user plane.

The Non-Access Stratum (NAS) layer in the upper of the RRC layerperforms the function of session management, mobility management, and soon.

A cell constituting the base station is set to one of 1.25, 2.5, 5, 10,and 20 MHz bandwidth, providing downlink or uplink transmission servicesto a plurality of UEs. Different cells can be set to differentbandwidths.

Downlink transport channels transmitting data from a network to a UEinclude a Broadcast Channel (BCH) transmitting system information, PCHtransmitting paging messages, DL-SCH transmitting user traffic orcontrol messages, and so on. Traffic or a control message of a downlinkmulti-cast or broadcast service can be transmitted through the DL-SCH orthrough a separate downlink Multicast Channel (MCH). Meanwhile, uplinktransport channels transmitting data from a UE to a network include aRandom Access Channel (RACH) transmitting the initial control messageand a Uplink Shared Channel (UL-SCH) transmitting user traffic orcontrol messages.

Logical channels, which are located above the transport channels and aremapped to the transport channels. The logical channels may bedistinguished by control channels for delivering control areainformation and traffic channels for delivering user area information.The control channels include a Broadcast Control Channel (BCCH), aPaging Control Channel (PCCH), a Common Control Channel (CCCH), adedicated control channel (DCCH), a Multicast Control Channel (MCCH),and etc. The traffic channels include a dedicated traffic channel(DTCH), and a Multicast Traffic Channel (MTCH), etc. The PCCH is adownlink channel that delivers paging information, and is used whennetwork does not know the cell where a UE belongs. The CCCH is used by aUE that does not have RRC connection with network. The MCCH is apoint-to-multipoint downlink channel which is used for deliveringMultimedia Broadcast and Multicast Service (MBMS) control informationfrom network to UE. The DCCH is a point-to-point bi-directional channelwhich is used by a UE that has RRC connection delivering dedicatedcontrol information between UE and network. The DTCH is a point-to-pointchannel which is dedicated to a UE for delivering user information thatmay be existed in uplink and downlink. The MTCH is a point-to-multipointdownlink channel for delivering traffic data from network to UE.

In case of uplink connection between the logical channel and thetransport channel, the DCCH may be mapped to UL-SCH, the DTCH may bemapped to UL-SCH, and the CCCH may be mapped to UL-SCH. In case ofdownlink connection between the logical channel and the transportchannel, the BCCH may be mapped to BCH or DL-SCH, the PCCH may be mappedto PCH, the DCCH may be mapped to DL-SCH, the DTCH may be mapped toDL-SCH, the MCCH may be mapped to MCH, and the MTCH may be mapped toMCH.

FIG. 5 is a diagram schematically exemplifying a structure of physicalchannel in a wireless communication system to which the presentinvention can be applied.

Referring to FIG. 5, the physical channel delivers signaling and datathrough radio resources including one or more subcarriers in frequencydomain and one or more symbols in time domain.

One subframe that has a length of 1.0 ms includes a plurality ofsymbols. A specific symbol (s) of subframe (e.g., the first symbol ofsubframe) may be used for PDCCH. The PDCCH carries information forresources which are dynamically allocated (e.g., resource block,modulation and coding scheme (MCS), etc.).

Random Access Procedure

Hereinafter, a random access procedure which is provided in a LTE/LTE-Asystem will be described.

The random access procedure is performed in case that the UE performs aninitial access in a RRC idle state without any RRC connection to an eNB,or the UE performs a RRC connection re-establishment procedure, etc.

The LTE/LTE-A system provides both of the contention-based random accessprocedure that the UE randomly selects to use one preamble in a specificset and the non-contention-based random access procedure that the eNBuses the random access preamble that is allocated to a specific UE.

FIG. 6 is a diagram for describing the contention-based random accessprocedure in the wireless communication system to which the presentinvention can be applied.

(1) Message 1 (Msg 1)

First, the UE randomly selects one random access preamble (RACHpreamble) from the set of the random access preamble that is instructedthrough system information or handover command, selects and transmitsphysical RACH (PRACH) resource which is able to transmit the randomaccess preamble.

The eNB that receives the random access preamble from the UE decodes thepreamble and acquires RA-RNTI. The RA-RNTI associated with the PRACH towhich the random access preamble is transmitted is determined accordingto the time-frequency resource of the random access preamble that istransmitted by the corresponding UE.

(2) Message 2 (Msg 2)

The eNB transmits the random access response that is addressed toRA-RNTI that is acquired through the preamble on the Msg 1 to the UE.The random access response may include RA preamble index/identifier, ULgrant that informs the UL radio resource, temporary cell RNTI (TC-RNTI),and time alignment command (TAC). The TAC is the information indicatinga time synchronization value that is transmitted by the eNB in order tokeep the UL time alignment. The UE renews the UL transmission timingusing the time synchronization value. On the renewal of the timesynchronization value, the UE renews or restarts the time alignmenttimer. The UL grant includes the UL resource allocation that is used fortransmission of the scheduling message to be described later (Message 3)and the transmit power command (TPC). The TCP is used for determinationof the transmission power for the scheduled PUSCH.

The UE, after transmitting the random access preamble, tries to receivethe random access response of its own within the random access responsewindow that is instructed by the eNB with system information or handovercommand, detects the PDCCH masked with RA-RNTI that corresponds toPRACH, and receives the PDSCH that is indicated by the detected PDCCH.The random access response information may be transmitted in a MACpacket data unit and the MAC PDU may be delivered through PDSCH.

The UE terminates monitoring of the random access response ifsuccessfully receiving the random access response having the randomaccess preamble index/identifier same as the random access preamble thatis transmitted to the eNB. Meanwhile, if the random access responsemessage has not been received until the random access response window isterminated, or if not received a valid random access response having therandom access preamble index same as the random access preamble that istransmitted to the eNB, it is considered that the receipt of randomaccess response is failed, and after that, the UE may perform theretransmission of preamble.

(3) Message 3 (Msg 3)

In case that the UE receives the random access response that iseffective with the UE itself, the UE processes the information includedin the random access response respectively. That is, the UE applies TACand stores TC-RNTI. Also, by using UL grant, the UE transmits the datastored in the buffer of UE or the data newly generated to the eNB.

In case of the initial access of UE, the RRC connection request that isdelivered through CCCH after generating in RRC layer may be transmittedwith being included in the message 3. In case of the RRC connectionreestablishment procedure, the RRC connection reestablishment requestthat is delivered through CCCH after generating in RRC layer may betransmitted with being included in the message 3. Additionally, NASaccess request message may be included.

The message 3 should include the identifier of UE. There are two wayshow to include the identifier of UE. The first method is that the UEtransmits the cell RNTI (C-RNTI) of its own through the UL transmissionsignal corresponding to the UL grant, if the UE has a valid C-RNTI thatis already allocated by the corresponding cell before the random accessprocedure. Meanwhile, if the UE has not been allocated a valid C-RNTIbefore the random access procedure, the UE transmits including uniqueidentifier of its own (for example, SAE temporary mobile subscriberidentity (S-TMSI) or random number). Normally the above uniqueidentifier is longer that C-RNTI.

If transmitting the data corresponding to the UL grant, the UE initiatesa contention resolution timer.

(4) Message 4 (Msg 4)

The eNB, in case of receiving the C-RNTI of corresponding UE through themessage 3 from the UE, transmits the message 4 to the UE by using thereceived C-RNTI. Meanwhile, in case of receiving the unique identifier(that is, S-TMSI or random number) through the message 3 from the UE,the eNB transmits the 4 message to the UE by using the TC-RNTI that isallocated from the random access response to the corresponding UE. Forexample, the 4 message may include the RRC connection setup message.

The UE waits for the instruction of eNB for collision resolution aftertransmitting the data including the identifier of its own through the ULgrant included the random access response. That is, the UE attempts thereceipt of PDCCH in order to receive a specific message. There are twoways how to receive the PDCCH. As previously mentioned, in case that themessage 3 transmitted in response to the UL grant includes C-RNTI as anidentifier of its own, the UE attempts the receipt of PDCCH using theC-RNTI of itself, and in case that the above identifier is the uniqueidentifier (that is, S-TMSI or random number), the UE tries to receivePDCCH using the TC-RNTI that is included in the random access response.After that, in the former case, if the PDCCH is received through theC-RNTI of its own before the contention resolution timer is terminated,the UE determines that the random access procedure is performed andterminates the procedure. In the latter case, if the PDCCH is receivedthrough the TC-RNTI before the contention resolution timer isterminated, the UE checks on the data that is delivered by PDSCH, whichis addressed by the PDCCH. If the content of the data includes theunique identifier of its own, the UE terminates the random accessprocedure determining that a normal procedure has been performed. The UEacquires C-RNTI through the 4 message, and after that, the UE andnetwork are to transmit and receive a UE-specific message by using theC-RNTI.

Meanwhile, the operation of the non-contention-based random accessprocedure, unlike the contention-based random access procedureillustrated in FIG. 11, is terminated with the transmission of message 1and message 2 only. However, the UE is going to be allocated a randomaccess preamble from the eNB before transmitting the random accesspreamble to the eNB as the message 1. And the UE transmits the allocatedrandom access preamble to the eNB as the message 1, and terminates therandom access procedure by receiving the random access response from theeNB.

MTC (Machine-Type Communication)

FIG. 7 is a diagram illustrating a MTC (Machine-Type Communication)architecture in a wireless communication system to which the presentinvention may be applied.

An end-to-end application between the UE (or MTC terminal) used for theMTC and the MTC application can utilize the services provided in the3GPP system and the optional services provided to the MTC server. The3GPP system can provide transport and communication services (including3GPP bearer services, IMS and Short Message Service (SMS)) includingvarious optimizations which facilitate the MTC.

Referring to FIG. 7, the UE used for MTC is connected to a 3GPP network(UTRAN, E-UTRAN, GERAN, I-WLAN, etc.) through the Um/Uu/LTE-Uuinterface. The architecture of FIG. 7 includes various MTC models(Direct, Indirect, Hybrid).

First, the entities shown in FIG. 7 will be described.

In FIG. 7, the application server is a server on the network where theMTC application is executed. The technologies for implementing variousabove-described MTC applications can be applied to the MTC applicationserver, and the detailed description thereof will be omitted here. InFIG. 7, the MTC application server can access the MTC server through thereference point API, and the detailed description thereof will beomitted here. Alternatively, the MTC application server may becollocated with the MTC server.

The MTC server (for example, the SCS server in FIG. 7) is a server onthe network that manages the MTC UE and can communicate with UEs andPLMN nodes which are connected to the 3GPP network and used for the MTC.

The MTC-IWF (MTC-InterWorking Function) may manage the interworkingbetween the MTC server and the operator core network, and play the roleof a proxy for the MTC operation. In order to support the MTC indirector hybrid model, the MTC-IWF can relay or interpret the signalingprotocol on the reference point Tsp to operate certain functions in thePLMN. The MTC-IWF may perform a function of authenticating the MTCserver before establishing communication with the 3GPP network, afunction of authenticating the control plane request from the MTCserver, various functions related to the trigger instruction describedlater, etc.

Short Message Service-Service Center (SMS-SC)/Internet Protocol ShortMessage GateWay (IP-SM-GW) can manage transmission and reception ofshort message service (SMS). The SMS-SC may be responsible for relaying,storing, and delivering short messages between a Short Message Entity(SME) (the entity transmitting or receiving short messages) and the UE.The IP-SM-GW can be in charge of protocol interoperability between theIP-based UE and the SMS-SC.

Charging Data Function (CDF)/Charging Gateway Function (CGF) can performcharging-related operations.

The HLR/HSS can store subscriber information (IMSI, etc.), routinginformation, setting information, and provide the MTC-IWF with thestored information.

The MSC/SGSN/MME may perform control functions such as mobilitymanagement, authentication and resource allocation for networkconnection of the UE. The MSC/SGSN/MME may perform a function ofreceiving a trigger instruction from the MTC-IWF in connection with thetriggering to be described later and processing the instruction in theform of a message to be provided to the MTC UE.

The Gateway GPRS Support Node (GGSN)/Serving-Gateway (S-GW)+Packet DateNetwork-Gateway (P-GW) can function as a gateway which is in charge ofconnection between the core network and the external network.

Table 2 summarizes the main reference points in FIG. 7.

TABLE 2 Reference point Description Tsms A reference point used by anentity outside the 3GPP system to communicate with the MTC UE via SMSTsp A reference point used by an entity outside the 3GPP system tocommunicate with the MTC-IWF in connection with control plane signalingT4 A reference point used by the MTC-IWF to route the device trigger tothe SMS-SC of the HPLMN T5a A reference point between the MTC-IWF andthe serving SGSN T5b A reference point between the MTC-IWF and theserving MME T5c A reference point between the MTC-IWF and the servingMSC S6m A reference point used by the MTC-IWF to inquire the UE'sidentification information (E.164 Mobile Station InternationalSubscriber Directory Number (MSISDN) or IMSI mapped to an externalidentifier) and to collect UE accessibility and setting information

In Table 2, one or more of the reference points T5a, T5b, and T5c isreferred to as T5.

On the other hand, user plane communication with the MTC server in thecase of the indirect and hybrid models and communication with the MTCapplication server in the case of the direct and hybrid models can beperformed using the existing protocol through the reference points Giand SGi.

Specific details relating to the contents described with reference toFIG. 7 can be incorporated into this document by referring to the 3GPPTS 23.682 document.

FIG. 8 is a diagram illustrating an architecture for the servicecapability exposure in a wireless communication system to which thepresent invention may be applied.

The architecture for the service capability exposure illustrated in FIG.8 allows the 3GPP network to securely expose its services andcapabilities provided by the 3GPP network interface to an external thirdparty service provider application.

The Service Capability Exposure Function (SCEF) is a core entity withinthe 3GPP architecture for service capability exposure that provides ameans for securely exposing services and capabilities provided by 3GPPnetwork interfaces. In other words, the SCEF is a core entity forproviding service functions belonging to a trust domain operated by amobile communication provider. The SCEF provides API interfaces to thirdparty service providers and provides 3GPP service functions to the thirdparty service providers through connections with various entities of the3GPP. The SCEF function may also be provided by the SCS.

If the Tsp function can be exposed through an application programinterface (API), the MTC-IWF can be co-located with the SCEF. A protocol(e.g., DIAMETER, RESTful APIs, XML over HTTP, etc.) for specifying a new3GPP interface depending on multiple factors is selected. Here, themultiple factors may include easiness of exposure of requestedinformation or the need of a specific interface, but the presentinvention is not limited to these examples.

The SCEF is an entity that belongs to the Trust Domain and can beoperated by a cellular operator or by a third party that has a trustedrelationship. As a node for service architecture exposure performedunder work items such as MONTE (Monitoring Enhancement) and AESE(Architecture Enhancements for Service Capability Exposure) of 3GPPRelease 13, the SCEF is connected to 3GPP entities which is to provideservices as in FIG. 8 to thereby provide external third parties withvarious functions related to monitoring and charging fees and set thecommunication pattern of the third party providers to the inside of EPS.

RRC Connection Setup Procedure

FIG. 9 illustrates a legacy RRC connection procedure in a wirelesscommunication system to which the present invention may be applied.

FIG. 9 illustrates a current S1/EPS architecture based procedure (i.e.,an applicable procedure at transition of a UE idle/connection state)required to establish and tear down a connection so that the UE maytransmit/receive a user plane.

1. The UE transmits a random access (RA) first message (Msg 1) (i.e., apreamble) to the eNB.

2. The eNB sends an RA second message (Msg 2) (i.e., a random accessresponse) to the UE.

3. The UE sends an RA third message (Msg 3) to the eNB.

In this case, in the case of initial connection of the UE, an RRCconnection request for requesting RRC connection may be included in theRA Msg 3 and transmitted.

The RRC connection request message includes a UE identity (e.g., SAEtemporary mobile subscriber identity (S-TMSI) or random ID) and anestablishment cause.

The RRC establishment cause is determined according to an NAS procedure(e.g., attach, detach, tracking area update, service request, andextended service request).

4. The eNB transmits an RA fourth message (Msg 4) to the UE.

In this case, the eNB may transmit to the UE an RRC connection setupmessage in the RA Msg 4 in response to the RRC connection requestmessage.

After receiving the RRC connection setup message, the UE transitions tothe RRC_CONNECTED state.

5. The UE transmits to the network THE RRC connection setup completemessage to the eNB in order to verify successful completion of RRCconnection establishment.

In this case, the UE may transmit the RRC connection setup completemessage including an NAS message (for example, an initial attachmessage, a service request message (in the case of FIG. 9), etc.) to theeNB.

6. The eNB acquires a service request message from the RRC connectionsetup complete message and delivers the acquired service request messageto the MME through an S1AP initial UE Message.

The initial UE message includes a NAS message (e.g., the service requestmessage), a tracking area identity (TAI) and an E-UTRAN cell globalidentifier (ECGI) of the serving cell, S-TMSI, a closed subscriber group(CSG) identifier (ID), a CSG access mode, and an RRC establishmentcause.

7. The MME transmits an S1-AP initial context setup request message tothe eNB.

The initial context setup request message includes an S-GW address, anS1-tunnel endpoint identifier (TEID), an EPS Bearer QoS(s), a securityContext, an MME signaling connection Id, a handover restriction list,and a CSG membership indication.

8. The eNB transmits an RRC security mode command message containing theselected access stratum (AS) algorithm to the UE.

The RRC security mode command message is integrity protected with an RRCintegrity key based on a current access security management entity key(i.e., K_ASME).

9. The UE transmits an RRC security mode complete message to the eNB.

The RRC security mode complete is integrity protected with the selectedalgorithm indicated in the RRC security mode command message and theK_ASME based RRC integrity key.

10. The eNB transmits an RRC configuration reconfiguration message tothe UE in order to establish the radio bearer.

11. The UE transmits to the eNB an RRC connection reconfigurationcomplete message in response to the RRC connection reconfigurationmessage in order to verify successful completion of radio bearerestablishment.

After this step, uplink data may be delivered to the S-GW from the UE bythe eNB. The eNB may transmit the uplink data provided in step 7 aboveto the S-GW address and the TEID.

12. The eNB transmits the S1-AP initial context setup complete messageto the MME.

The initial context setup complete message includes an ENB address, alist of accepted EPS bearers, a list of rejected EPS bearers, and S1TEID(s) (DL).

13. The MME transmits a modify bearer request message to the S-GW foreach PDN connection.

The modify bearer request message includes the eNB address, S1 TEID(s)(DL) for the accepted EPS bearer, a delay downlink packet notificationrequest, an RAT type, and the like.

14. The S-GW transmits a modify bearer response message to the MME inresponse to the modify bearer request.

The modify bearer response message includes the S-GW address and theTEID for uplink traffic.

After this step, downlink data may be delivered to UE from the S-GW bythe eNB.

Meanwhile, for example, when a user inactivity is detected until apredetermined time elapses after a predetermined time has elapsed, an S1release procedure may be performed.

15. When the eNB detects that the signaling connection of the UE and allradio bearers for the UE need to be released, the eNB transmits a S1-APUE context release request message to the MME.

The UE context release request message includes a cause and the causeindicates a release cause (e.g., the user inactivity, etc.).

16. The MME transmits a release access bearers request message to theS-GW in order to request the release of all S1-U bearers for the UE.

17. When the S-GW receives the release access bearers request message,all ENB related information (i.e., address and TEID(s)) for thecorresponding UE is released and a release access bearers responsemessage is responded to the MME.

18. The MME releases S1 by transmitting an S1-AP UE context releasecommand message to the eNB.

19. The eNB transmits the RRC connection release message to the UE. Whenthe message is acknowledged by the UE, the eNB deletes the context ofthe UE.

20. The eNB acknowledges the release of the S by transmitting the S1-APUE context release command message to the MME.

Efficient Small Data Transmission for Narrowband Internet of Things(IOT)

In 3GPP, an architecture for a new core network for the efficient smalldata transmission is discussed in order to support narrowband Internetof things (NB-IoT).

FIG. 10 is a diagram illustrating an end to end small data flow in awireless communication system to which the present invention may beapplied.

As illustrated in FIG. 10, transmission and reception of non-Internetprotocol (IP) may be performed by a point-to-point tunnel scheme betweenthe AS and a CIoT serving gateway node (C-SGN). The C-SGN may be anintegrated node including a main function of the MME and a main functionof the S-GW in order to efficiently support the CIoT.

Alternatively, an SCEF framework may be used in order to transmit andreceive a non-IP packet. In other words, the transmission and receptionof the non-IP data may be performed via the SCEF between the AS/SCS andthe C-SGN.

In addition, the transmission and reception of the non-IP data may beperformed between the C-SGN and the UE through an S1-MME referencepoint. That is, small data (e.g., non-IP data) encrypted by the NASlayer may be transmitted and received between the UE and the C-SGN.

The C-SGN is a new logical entity and may be implemented to support onlyan essential function required for a CIoT use case as follows.

-   -   Some procedures required in a mobility management (MM)        procedure;    -   Efficient small data procedure;    -   Security procedure required for efficient small data;    -   SMS on a PS domain using a non-combined GPRS attach procedure        when a short message service (SMS) support is required;    -   Paging optimization for coverage enhancement;    -   Termination of an SGi interface for a non-roaming case;    -   Supporting an S8 interface for a roaming case;    -   Supporting an attach (that is, an attach for SMS transmission        and reception without the PDN connection for the IP (or non-IP)        data) procedure for only the SMS;    -   Supporting tunneling on SGi for the non-IP data.

As described above, a solution for small data transmission using theSCEF is discussed in the 3GPP and for NB-IOT, the following conclusionis reached.

For infrequent small data transmission (IP data, non-IP data, and SMS),a solution for supporting data transmission and reception through an NASPDU via a signaling radio bearer (SRB) between the UE and the networkbased on the architecture illustrated in FIG. 10 above is mandatorilyapplied.

A solution may be optionally applied, which requires data transmissionand reception through a data radio bearer (DRB) (S1-U), but caches ASparameters in the eNB even when the UE is switched from a connectedstate to an idle state.

The present invention may be applied even to the C-SGN defined as a newnode and further, may be applied even to a form in which a CIoT functionis added to the existing combination of the MME and the S-GW.

Cellular Internet of things (CIoT) EPS optimization is defined toefficiently serve a low complexity UE such as NB-IoT and LTE MTC. Thatis, the CIoT EPS optimization provides an enhanced support for the smalldata transmission.

At present, control plane (CP) CIoT EPS optimization or CIoT EPS CPOptimization and CIoT EPS user plane (UP) optimization or CIoT EPS UPoptimization to transmit data to the SRB are defined and the same UE maysupport both two different data transmission modes.

The CP CIoT EPS optimization supports efficient delivery of the userdata (IP, non-IP, or SMS) through the control plane via the MME withouttriggering establishment of the data radio bearer. Optionally, headercompression of the IP data may be applied to IP PDN type PDN connectionconfigured to support the header compression.

The UP CIoT EPS optimization supports a change from an EMM-idle mode toan EMM-connected mode without using the service request procedure.

During the attach or tracking area update (TAU) of the UE, a capability(that is, CIoT EPS optimization supported by the UE and/or MME) for theCIoT EPS optimization may be negotiated with the MME. In other words,the UE that supports the CIoT EPS optimization may indicate a CIoTnetwork operation which the UE may support and prefer to use during theattach or TAU procedure.

For example, when the UE supports both two types of CIoT EPSoptimizations, the MME may also approve the PDN connection in which twoCIoT EPS optimizations are available. As one example, in the case of aPDN connection requiring data transmission/reception with the SCEF, theMME may transmit an instruction to the UE to communicate with the CPonly (that is, using the CP CIoT EPS optimization only). In this case,the UE may select a transmission format by an application requiringcurrent mobile originated (MO) transmission and a policy of acorresponding access point name (APN).

The UE may request an appropriate data transmission format (i.e., CPCIoT EPS optimization or UP CIoT EPS optimization) for RRC connectionswitching as follows.

FIG. 11 is a diagram illustrating CP CIoT EPS optimization and UP CIoTEPS optimization for mobile originated data in a wireless communicationsystem to which the present invention may be applied.

0. The UE is in EPS connection management (ECM)-idle.

First, when the CP CIoT EPS optimization is used (A), a transmissionprocedure of the uplink data will be described.

1. The UE establishes the RRC connection and transmits the NAS PDUintegrity protected as a part of the establishment of the RRC connectionto the eNB. The NAS PDU carries the EPS bearer ID and the encrypteduplink data.

2. The NAS PDU transmitted in step 1 above is relayed to the MME byusing the S1-AP initial UE message by the eNB.

3. The MME checks integrity of the received NAS PDU and decrypts dataincluded in the NAS PDU.

4. When S11-U connection is not established, the MME transmits themodify bearer request message to the S-GW for each PDN connection.

The modify bearer request message includes an MME address, MME TEID DL,a delay downlink packet notification request, the RAT type, and thelike.

The S-GW may now transmit the downlink data to the UE.

5-6. The S-GW transmits the modify bearer response message to the P-GWand the P-GW transmits the modify bearer response message to the S-GW.

7. When the modify bearer request message is transmitted in step 4, theS-GW transmits the modify bearer response message to the MME in responseto the modify bearer request message.

The modify bearer response message includes an S-GW address and a TEIDfor uplink traffic.

An S-GW address and an S-GW TEID for an S11-U user plane are used todeliver the uplink data to the S-GW by the MME.

8. The MME transmits the uplink data to the P-GW via the S-GW.

9. The MME may transmit a connection establishment indication message tothe eNB.

10. The UE may transmit to the eNB an uplink (UL) information transfermessage including the integrity protected NAS PDU.

11. The NAS PDU transmitted in step 10 may be relayed to the MME byusing an S1-AP uplink transport message by the eNB.

12. The MME may transmit the uplink data to the P-GW via the S-GW.

Next, when the UP CIoT EPS optimization is used (B), the transmissionprocedure of the uplink data will be described.

1. The UE establishes the RRC connection and transmits a NAS servicerequest message to the eNB as a part of the establishment of the RRCconnection.

2. The eNB acquires the NAS service request message from the RRCconnection setup complete message and delivers the acquired NAS servicerequest message to the MME through the S1AP initial UE Message.

3. An NAS authentication/security procedure may be performed.

4. The MME transmits the modify bearer request message to the S-GW foreach PDN connection.

The modify bearer request message includes the eNB address, the S1TEID(s) (DL) for the accepted EPS bearer, the delay downlink packetnotification request, the RAT type, and the like.

5-6. The S-GW transmits the modify bearer response message to the P-GWand the P-GW transmits the modify bearer response message to the S-GW.

7. The S-GW transmits a modify bearer response message to the MME inresponse to the modify bearer request.

The modify bearer response message includes the S-GW address and theTEID for the uplink traffic.

8. The MME transmits the S1-AP initial context setup request message tothe eNB.

9. The radio bearer is set up between the UE and the eNB.

10. The uplink data is transferred from the UE to the S-GW by the eNBand transferred to the P-GW via the S-GW.

Further, the MME may also select a CIoT EPS optimization modeappropriate to the mobile terminated (MT) data as follows.

FIG. 12 is a diagram illustrating CP CIoT EPS optimization and UP CIoTEPS optimization for mobile terminated data in a wireless communicationsystem to which the present invention may be applied.

0. The UE is attached to the EPS and is in the ECM-idle mode.

1. When the S-GW receives the downlink data packet/control signaling forthe UE, the S-GW buffers the downlink data packet and identifies whichMME serves the corresponding UE.

2. When the S-GW is buffering data in step 1, the S-GW transmits adownlink data notification message to the MME with control planeconnectivity for the corresponding UE.

The downlink data notification message includes an allocation/retentionpriority (ARP) and the EPS bearer ID.

The MME responds to the S-GW with a downlink data notification Ackmessage.

3. When the UE is registered in the MME and it is determined that the UEis reachable, the MME transmits a paging message to each ENB whichbelongs to a tracking area(s) in which the UE is registered.

The paging message includes an NAS identifier (ID) for paging, TAI(s), aUE identity based discontinuous reception (DRX) index, a paging DRXlength, a list of CSG ID(s) for paging, and a paging priorityindication.

4. When the eNB receives the paging message from the MME, the UE ispaged by the eNB.

5. Since the UE is in the ECM-idle state, the UE transmits an NAScontrol plane service request message through the RRC connection requestand the S1-AP initial UE message.

6. The eNB acquires the control plane service request message from theRRC connection request message and delivers the acquired control planeservice request message to the MME through the S1AP initial UE message.

First, when the CP CIoT EPS optimization is used (A), the transmissionprocedure of the uplink data will be described.

7. When the S11-U connection is not established, the MME transmits themodify bearer request message to the S-GW for each PDN connection.

The modify bearer request message includes the MME address, the MME TEIDDL, the delay downlink packet notification request, the RAT type, andthe like.

The S-GW may now transmit the downlink data to the UE.

8-9. The S-GW transmits the modify bearer response message to the P-GWand the P-GW transmits the modify bearer response message to the S-GW.

10. When the modify bearer request message is transmitted in step 7, theS-GW transmits the modify bearer response message to the MME in responseto the modify bearer request message.

The modify bearer response message includes the S-GW address and theTEID for the uplink traffic.

The S-GW address and the S-GW TEID for the S11-U user plane are used todeliver the uplink data to the S-GW by the MME.

11. The buffered (when the S11-U is not established) downlink data istransmitted to the MME by the S-GW.

12-13. The MME encrypts and integrity protects the downlink data. Inaddition, the MME transmits the downlink data to the eNB by using theNAS PDU transferred by the downlink S1-AP message.

14. The NAS PDU accompanying the data is transferred to the UE throughthe downlink RRC message. This is handled as an implicit acknowledgmentof the service request message transmitted in step 5 above by the UE.

15. While the RRC connection is still established, additional uplink anddownlink data may be transferred by using the NAS PDU(s). In step 15,transfer of the uplink data using the uplink RRC message encapsulatingthe NAS PDU accompanying the data is exemplified.

16. The NAS PDU accompanying the data is transmitted to the MME withinthe uplink S1-AP message.

17. The integrity of the data is checked and the data is decrypted.

18. The MME transmits the uplink data to the P-GW via the S-GW.

19. When the eNB detects that there is no more activity, step 20 isperformed.

20. The eNB starts an eNodeB initiated S1 release procedure.

Next, when the UP CIoT EPS optimization is used (B), the transmissionprocedure of the uplink data will be described.

7. The NAS authentication/security procedure may be performed.

8. The MME transmits the S1-AP initial context setup request message tothe eNB.

9. An RRC reconfiguration procedure is performed between the UE and theeNB.

10. The uplink data is transferred to the S-GW from the UE by the eNB.

11. The eNB transmits the S1-AP initial context setup complete messageto the MME.

The initial context setup complete message includes the ENB address, thelist of accepted EPS bearers, the list of rejected EPS bearers, and theS1 TEID(s) (DL).

12. The MME transmits the modify bearer request message to the S-GW foreach PDN connection.

The modify bearer request message includes the eNB address, the S1TEID(s) (DL) for the accepted EPS bearer, the delay downlink packetnotification request, the RAT type, and the like.

13-14. The S-GW transmits the modify bearer response message to the P-GWand the P-GW transmits the modify bearer response message to the S-GW.

15. The S-GW transmits a modify bearer response message to the MME inresponse to the modify bearer request.

The modify bearer response message includes the S-GW address and theTEID for the uplink traffic.

16. When the eNB detects that there is no more activity, step 19 isperformed.

19. The eNB starts the eNodeB initiated S1 release procedure.

Release Assistance Indication/Information (RAI)

The RAI means assistance information for rapid connection release of theUE. When the UE transmits data by using the CP CIoT EPS optimization,the UE may transmit the data additionally including the RAI. Forexample, in step 1 of FIG. 11 above, the UE may transmit the NAS PDUincluding the RAI.

An RAI information element (IE) is used to notify to the network whetheronly single downlink data transmission (e.g., an acknowledgement or aresponse to the uplink data) subsequent to the uplink data transmissionis expected or whether additional uplink or downlink transmission isexpected.

The RAI IE may be coded as illustrated in FIG. 13 and Table 3.

The RAI IE is type 1 IE.

FIG. 13 is a diagram illustrating a release assistanceindication/information information element in a wireless communicationsystem to which the present invention may be applied.

Referring to FIG. 13, the RAI IE has a length of 1 octet and 4 bits(i.e., 5 to 8 bits) from the most significant bit (MSB) (or left-mostbit)) represent an information element identifier (IEI), the next 1 bit(i.e., bit 4) represents a spare bit, and the next one bit (i.e., bit 3)represents the spare bit, and the next two bits represent downlink dataexpected (DDX).

Table 3 illustrates a description based on a value of the DDX.

TABLE 3 Release assistance indication value Downlink data expected (DDX)Bits 2 1 0 0 No information available 0 1 Downlink data transmissionsubsequent to the uplink data transmission is not expected 1 0 Downlinkdata transmission subsequent to the uplink data transmission is expected1 1 Reserved 3 and 4 bits in 1 octet are spare and encoded with 0

Tracking Area Update/Updating (TAU) Procedure

The TAU procedure as one of the mobility management procedures performedby the MME is one of the important functions for managing the mobilityof the UE in the EPS.

Mobility based TAU may be performed when entrance into a new trackingarea (TA) that does not exist in the list of tracking area identity(s)is detected (i.e., when the tracking area is changed).

Further, when a periodic TAU (P-TAU) timer set in the UE expires afterthe UE enters the idle mode, a periodic TAU procedure may be performed.The periodic TAU may be a method for reachability checking for checkingthe UE effectively exists in the network of the UE.

FIG. 14 illustrates a tracking area update procedure in a wirelesscommunication system to which the present invention may be applied.

FIG. 14 illustrates a TAU procedure accompanying a change of the S-GW.

1. One of predetermined triggers for the start of the TAU procedureoccurs, such as a case where the TAU timer of the UE which is in an EPSconnection management (ECM)-idle state expires or the UE moves toanother tracking area.

2. The UE initiates the TAU procedure by transmitting the TAU requestmessage to the eNB together with an RRC parameter indicating theselected network and an old globally unique MME identifier (GUMMEI).

The TAU request message may include a UE core network capability, amobile station (MS) network capability, a preferred network behavior, anold globally unique temporary identity (GUTI), an old GUTI type, a lastvisited TAI, an active flag, an EPS bearer status, a packet temporarymobile subscription (P-TMSI) signature, an additional GUTI, a key setidentifier for E-UTRAN, an NAS sequence number, an NAS-messageauthentication code (MSC), a key set identifier (KSI), and voice domainpreference and UE's usage setting.

The active flag is a request by the UE for activation of a radio bearerand an S1 bearer for all active EPS bearer(s) by the TAU procedure whenthe UE is in the ECM-IDLE state. The EPS bearer status indicates eachbearer which is active in the UE.

In the case of the UE using CIoT EPS Optimization having no active PDNconnection, the active flag or EPS bearer status is not included in theTAU request message.

3. The ENB derives the MME address from the old GUMMEI, the indicatedselected network, and the RRC parameter carrying the RAT. Further, theMME address may be derived based on RRC CIoT EPS optimizationinformation.

The eNB transfers to the MME the TAU request message together with theCSG access mode, the CSG ID, TAI+ECGI, RAT type of a cell receiving theTAU request message, and the selected network.

4. New MME uses the GUTI received from the UE in order to differentiatea type of old node (that is, MME or SGSN) and derive an old MME/S4 SGSNaddress. In addition, the new MME transmits the context request messageto the old MME/old S4 SGSN in order to acquire user information.

The context request message may include an old GUTI, a complete TAUrequest message, P-TMSI Signature, the MME address, UE validated, and aCIoT EPS optimization support indication.

When the new MME supports the CIoT EPS optimization, the CIoT EPSoptimization support indication is included in the context requestmessage indicating the support (for example, supporting the headercompression for CP optimization) of various CIoT EPS optimizations.

5. When the context request is transmitted to the old MME, the old MMEresponds with the context response message.

The context response message may include IMSI, mobile equipment (ME)identity (International mobile station equipment identity and softwareversion number (IMEISV)), a mobility management (MM) context, EPS bearercontext(s), a signaling address and TEID(s) of the S-GW, idle modesignaling (ISR) reduction supported, MS information change reportingaction (when usable), CSG information reporting action (when usable), aUE time zone, a UE core network capability, and UE specific DRXparameter(s).

When the new MME supports the CIoT EPS optimization and a robust headercompression (RoHC) context to the UE exists, the context responsemessage includes a header compression configuration.

In the case of the UE using CIoT EPS Optimization having no active PDNconnection, the EPS bearer context(s) is(are) not included in thecontext response message.

Based on the CIoT EPS Optimization support indication, the old MMEtransfers only EPS bearer context(s) supported by the new MME. When thenew MME does not support the CIoT EPS Optimization, EPS bearercontext(s) of non-IP PDN connection is(are) not transferred to the newMME. When the EPS bearer context(s) of the PDN connection is(are) nottransferred, the old MME regards that all bearers for the correspondingPDN connection are unsuccessful and triggers an MME requested PDNdisconnection procedure to release the corresponding PDN connection. Thedata buffered in the old MME is discarded after receiving the contextacknowledge message.

6. When integrity check of the TAU request message transmitted in step 2above is unsuccessful, the authentication is mandatory.

7. The MME (that is, in the case of the new MME by the change of theMME) determines relocation of the S-GW. When an old S-GW may notcontinuously serve the UE, the S-GW is relocated. The MME (that is, inthe case of the new MME by the change of the MME) may also determinerelocation of the S-GW when it is expected that the new S-GW serves theUE for a longer time and/or when the new S-GW is further optimized interms of a P-GW path or when the new S-GW may be co-located with theP-GW.

When the MME is changed, the new MME transmits the context acknowledgemessage to the old MME/old S4 SGSN.

The context acknowledge message includes an S-GW change indication.

The UE who uses the CIoT EPS Optimization with no active PDN connectionskips steps 8, 9, 10, 11, 18, and 19.

8. When the MME is changed, the new MME verifies the EPS bearer statusreceived from the UE using the bearer context received from the oldMME/old S4 SGSN. When the MME is not changed, the MME verifies the EPSbearer status from the UE using the bearer context usable in the MMcontext.

The MME released any network resource associated with the inactive EPSbearer(s) in the UE. When there is no bearer context, the MME rejectsthe TAU request.

When the MME selects the new S-GW, the MME transmits a Create SessionRequest message to the selected new S-GW for each PDN connection.

The Create Session Request message may include the IMSI, the bearercontext(s), the MME address and TEID, the type, protocol type overS5/S8, the RAT type, a serving network, and the UE time zone.

When the new MMF receives the EPS bearer context accompanying the SCEF,the new MME updates the SCEF.

9. The S-GW transmits the Modify Bearer Request message to the P-GW(s)for each PDN connection.

The Modify Bearer Request message may include the S-GW address and TEID,the RAT type, the serving network, and a PDN charging pause supportindication.

9a. When dynamic policy and charging control (PCC) is deployed and RATtype information needs to be delivered from the P-GW to a Policy andCharging Rules Function (PCRF), the P-GW transmits the RAT typeinformation to the PCRF using an IP connectivity access network (IP-CAN)session modification procedure.

10. The P-GW updates the bearer context thereof and sends the ModifyBearer Response message to the S-GW.

The Modify Bearer Response message may include an MSISDN, a charging Id,and a PDN Charging Pause Enabled Indication (when the P-GW selectsactivation of this function).

11. The S-GW updates the bearer context thereof. Therefore, when theS-GW receives bearer PDU(s) from the eNB, the S-GW may route the bearerPDU(s) to the P-GW.

The S-GW transmits a Create Session Response message to the MME.

The Create Session Response message may include the S-GW address andTEID for the user plane and the control plane, the P-GW TEID(s) (in thecase of GPRS Tunneling Protocol (GTP)-based S5 S8) or GRE key(s) (in thecase of Proxy Mobile IP (PMIP)-based S5/S8) for the uplink traffic andcontrol plane, and MS Info Change Reporting Action.

12. The new MME verifies whether the subscription data for the UEidentified by the IMSI received with the context data from the GUTI,additional GUTI, or old CN node is held.

When there is no subscription data for the UE in the new MME, the newMME transmits an Update Location Request message to the HSS.

The Update Location Request message may include an MME identity (IMSI),Update Location Request Flags (ULR-flag(s)), MME capabilities,Homogeneous Support of IMS Voice over packet switched (PS) Sessions, aUE single radio voice call continuity (SRVCC) capability, an equivalentPLMN list, and an ME identity (IMEISV).

13. The HSS transmits a Cancel Location message with the CancellationType set by the update procedure to the old MME.

The Cancel Location message may include the IMSI and the CancellationType.

14. When the timer started in step 4 above is not driven, the old MMEremoves the MM context. Otherwise, the context is removed when the timerexpires.

The old MME responds to the HSS with a Cancel Location Ack messagecontaining the IMSI.

15. When the old S4 SGSN receives the Context Acknowledge message andthe UE is in the Iu connection state, the old S4 SGSN transmits an IuRelease Command message to the RNC after the timer started in step 4expires.

16. The RNC responds with an Iu Release Complete message.

17. The HSS transmits to the new MME the Update Location Ack messageincluding the subscription data to acknowledge the Location UpdateRequest message.

18. When the MME is changed, the old MME/old S4 SGSN releases the localMME or SGSN bearer resources when the timer started in step 4 aboveexpires. Additionally, when the S-GW change indication in the ContextAcknowledge message is received in step 7, the old MME/old SGSNtransmits a Delete Session Request message including a cause and anOperation Indication to the old S-GW to delete the EPS bearer resource.

When the MME is not changed, the old S-GW triggers the release of theEPS bearer resource in step 11.

19. The S-GW acknowledges with a Delete Session Response messageincluding the cause.

The S-GW discards any packet buffered for the corresponding UE.

20. The MME transmits a TAU Accept message to the UE.

The TAU Accept message may include GUTI, TAI list, EPS bearer status,NAS sequence number, NAS-MAC, IMS Voice over PS session supported,Emergency Service Support indicator, Location Service (LCS) SupportIndication, and Supported Network Behavior.

When the active flag is set, the MME may provide a Handover RestrictionList to the eNB. When the MME allocates new GUTI, the GUTI is includedin the TAU Accept message. If the active flag is set in the TAU Requestmessage, the user plane setup procedure is activated with the TAU Acceptmessage. When the DL Data Buffer Expiration Time for the UE in the MMEexpires, the user plane setup procedure is activated even though the MMEdoes not receive the active flag in the TAU Request message. Even if thenew MME does not receive the active flag in the TAU Request message whenthe new MME receives the Downlink Data Notification message or anydownlink signaling message while the UE is still connected, the userplane setup procedure is activated.

In the case of the UE using CIoT EPS Optimization having no active PDNconnection, the EPS bearer status is not included in the TAU requestmessage.

21. When the GUTI is included in the TAU Accept, the UE acknowledges thereceived message by transmitting a TAU Complete message to the MME.

When the active flag is not set in the TAU Request message and the TAUis not initiated in the ECM-CONNECTED state, the new MME releases thesignaling connection with the UE according to the S1 release procedure.

After the new MME performs the security function or after the new MMEwaits for completion of the TAU procedure, the new MME may initiateestablishment of E-UTRAN Radio Access Bearer (E-RAB). For the UE, theE-RAB establishment may occur at any time after the TAU request istransmitted.

FIG. 15 illustrates a tracking area update procedure in a wirelesscommunication system to which the present invention may be applied.

FIG. 15 illustrates a TAU procedure accompanying a change of the S-GWand data transfer.

Procedures (A) and (B) in FIG. 15 are defined in FIG. 14 above. In FIG.15, step 5 differs from FIG. 14 only in one additional parameter, whichwill be described below.

5. The downlink data is buffered in the old S-GW and when the DL DataExpiration Time does not expire, the old MME/old S4-SGSN indicatesbuffered DL Data Waiting in the Context Response message. This triggersthe new MME to set up the user plane and invoke the data transfer.

In the case of the CP CIoT EPS Optimization, when the downlink data isbuffered in the old S-GW and when the Buffered DL Data Waiting isindicated, the new MME sets up the S11 user plane with the new S-GW andinvokes the data transfer.

When the downlink data is buffered in the old MME and the DL DataExpiration Time does not expire, the old MME discards the buffereddownlink data.

11-12. The user plane is set up.

In the case of the CP CIoT EPS Optimization, step 11 is skipped. In step12, the MME encapsulates the MME address and MME DL TEID in the ModifyBearer Request message and the S-GW encapsulates the S-GW address andS-GW uplink TEID in the Modify Bearer Response message.

13. Since it is indicated that the buffered downlink data is waiting instep 5, the new MME transmits a Create Indirect Data Forwarding TunnelRequest to the S-GW to set up a forwarding parameter.

In this case, the Create Indirect Data Forwarding Tunnel Request messagemay include target eNB address(s) and TEID for forwarding.

The S-GW transmits a Create Indirect Data Forwarding Tunnel Responsemessage to the target MME.

In this case, the Create Indirect Data Forwarding Tunnel Responsemessage may include target S-GW address(s) and TEID(s) for forwarding.

In the case of the CP CIoT EPS Optimization, the new MME sets up theforwarding parameter by transmitting the Create Indirect Data ForwardingTunnel Request message to the S-GW.

In this case, the Create Indirect Data Forwarding Tunnel Request messagemay include the target MME address(s) and TEID for forwarding.

14. This step is defined in step 7 of FIG. 14 above. Additionally, thenew MME encapsulates an F-TEID and a Forwarding indication to which thebuffered downlink data is to be forwarded in the Context Acknowledgemessage. The F-TEID may be an F-TEID for indirect forwarding, which isreceived from step 13 above or an F-TEID of the eNB (when the eNBsupports forwarding).

15. The Modify Bearer Request (including F-TEID) message is transmittedto the old S-GW. The F-TEID is a forwarding F-TEID (F-TEID) to which thebuffered downlink data is to be forwarded.

16. The old S-GW forwards the buffered downlink data thereof to theF-TEID received in step 15 above. The buffered downlink data istransmitted to the UE through the radio bearer established in step 11above. In the case of the CP CIoT EPS Optimization, the buffereddownlink data is transmitted from the new S-GW to the new MME andtransmitted to the UE.

FIG. 16 illustrates a tracking area update procedure in a wirelesscommunication system to which the present invention may be applied.

FIG. 16 illustrates a TAU procedure without an S-GW change.

1. One of predetermined triggers for the start of the TAU procedureoccurs, such as a case where the TAU timer of the UE expires or the UEmoves to another tracking area.

2. The UE initiates the TAU procedure by transmitting the TAU requestmessage to the eNB together with an RRC parameter indicating theselected network and the old GUMMEI.

The TAU request message may include a UE core network capability, an MSnetwork capability, a preferred network behavior, an old GUTI, an oldGUTI type, a last visited TAI, an active flag, an EPS bearer status, apacket temporary mobile subscription (P-TMSI) signature, an additionalGUTI, a key set identifier for E-UTRAN, an NAS sequence number, anNAS-message authentication code (MSC), a key set identifier (KSI), andvoice domain preference and UE's usage setting.

The active flag is a request by the UE for activation of a radio bearerand an S1 bearer for all active EPS bearer(s) by the TAU procedure. TheEPS bearer state indicates each bearer which is active in the UE.

In the case of the UE using CIoT EPS Optimization having no active PDNconnection, the active flag or EPS bearer state is not included in theTAU request message.

3. The eNB derives the MME address from the old GUMMEI, the indicatedselected network, and the RRC parameter carrying the RAT. Further, theMME address may be derived based on RRC CIoT EPS optimizationinformation.

The eNB transfers to the MME the TAU request message together with theCSG access mode, the CSG ID, TAI+ECGI, RAT type of a cell receiving theTAU request message, and the selected network.

4. New MME uses the GUTI received from the UE in order to differentiatea type of old node (that is, MME or SGSN) and derive an old MME/S4 SGSNaddress. In addition, the new MME transmits the context request messageto the old MME/old S4 SGSN in order to acquire user information.

The context request message may include an old GUTI, a complete TAUrequest message, P-TMSI Signature, the MME address, UE validated, and aCIoT EPS optimization support indication.

When the new MME supports the CIoT EPS optimization, the CIoT EPSoptimization support indication is included in the context requestmessage indicating the support (for example, supporting the headercompression for CP optimization) of various CIoT EPS optimizations.

5. When the context request is transmitted to the old MME, the old MMEresponds with the context response message.

The context response message may include IMSI, ME identity (IMEISV),unused EPS authentication vectors, KSI_ASME, K_ASME, EPS bearercontext(s), a signaling address and TEID(s) of the S-GW, MS informationchange reporting action (when usable), CSG information reporting action(when usable), a UE time zone, a UE core network capability, and UEspecific DRX parameter(s).

When the new MME supports the CIoT EPS optimization and a robust headercompression (RoHC) context to the UE exists, the context responsemessage includes a header compression configuration.

In the case of the UE using CIoT EPS Optimization having no active PDNconnection, the EPS bearer context(s) is(are) not included in thecontext response message.

Based on the CIoT EPS Optimization support indication, the old MMEtransfers only EPS bearer context(s) supported by the new MME. When thenew MME does not support the CIoT EPS Optimization, EPS bearercontext(s) of non-IP PDN connection is(are) not transferred to the newMME. When the EPS bearer context(s) of the PDN connection is(are) nottransferred, the old MME regards that all bearers for the correspondingPDN connection are unsuccessful and triggers an MME requested PDNdisconnection procedure to release the corresponding PDN connection. Thedata buffered in the old MME is discarded after receiving the contextacknowledge message.

6. When integrity check of the TAU request message transmitted in step 2above is unsuccessful, the authentication is mandatory.

7. When the old node is the old MME, the new MME transmits the ContextAcknowledge message to the old MME.

When the old node is the old S4 SGSN, the MME transmits the ContextAcknowledge message to the old SGSN.

The UE who uses the CIoT EPS Optimization with no active PDN connectionskips steps 10, 11, 12, and 13.

9. When the MME is changed, the new MME adopts the bearer contextreceived from the old MME/SGSN as the EPS bearer context of the UE to beheld by the new MME.

The MME verifies the EPS bearer status received from the UE with the EPSbearer context and releases any network resource associated with theinactive EPS bearer in the UE. When there is no bearer context, the MMErejects the TAU request.

When the MME is changed, the new MME transmits the Modify Bearer Requestmessage to the S-GW for each PDN connection.

The Modify Bearer Request message may include a new MME address andTEID, ISR activated, and the RAT type.

In the case of the CP CIoT EPS Optimization, the downlink data isbuffered to the S-GW, this procedure is a TAU procedure without an MMEchange, the DL Data Buffer Expiration Time in the MM context for the UEin the MME or this procedure is a TAU procedure accompanying the MMEchange, and the old MME/old S4-SGSN indicates buffered DL Data Waitingin the Context Response message in step 5 above, the MME encapsulatesthe MME address and the MME downlink TEID in the Modify Bearer Request.

10. The S-GW transmits the Modify Bearer Request message (including theRAT type) to the P-GW(s) for each PDN connection.

11. When the dynamic PCC is deployed and the RAT type information or UElocation information needs to be forwarded from the P-GW to the PCRF,the P-GW transmits the information to the PCRF by using the IP CANSession Modification procedure.

12. The P-GW updates a context field thereof so that the downlink PDU isrouted to an accurate S-GW and sends the Modify Bearer Response message(including the MSISDN) to the S-GW.

13. The S-GW updates the bearer context thereof.

The S-GW transmits the Modify Bearer Response message to the MME inresponse to the Modify Bearer Request message.

The Modify Bearer Response message may include the S-GW address and TEIDfor the uplink traffic and the MS Info Change Reporting Action.

In the case of the CP CIoT EPS Optimization, when the MME address andthe MME downlink TEID are provided in step 9 above, the S-GWencapsulates the S-GW address and S-GW uplink TEID in the Modify BearerResponse message. The downlink data is transmitted from the S-GW to theMME.

14. The new MME verifies whether the subscription data for the UEidentified by the IMSI received with the context data from the GUTI,additional GUTI, or old CN node is held.

When there is no subscription data for the UE in the new MME, the newMME transmits the Update Location Request message to the HSS to informthe HSS of the change of the MME.

The Update Location Request message may include an MME identity, IMSI,Update Location Request Flags (ULR-flag(s)), MME capabilities,Homogeneous Support of IMS Voice over PS Sessions, a UE SRVCCcapability, an equivalent PLMN list, and an ME identity (IMEISV).

15. The HSS transmits a Cancel Location message with the CancellationType set by the update procedure to the old MME.

The Cancel Location message may include the IMSI and the CancellationType.

16. When the timer started in step 4 above is not driven at the time ofreceiving the Cancel Location message, the old MME removes the MMcontext. Otherwise, the context is removed when the timer expires.

The old MME responds to the HSS with the Cancel Location Ack messagecontaining the IMSI.

17. When the old S4 SGSN receives the Context Acknowledge message andthe UE is in the Iu connection state, the old S4 SGSN transmits an IuRelease Command message to the RNC after the timer started in step 4expires.

18. The RNC responds with the Iu Release Complete message.

19. The HSS transmits to the new MME the Update Location Ack messageincluding the subscription data to acknowledge the Location UpdateRequest message.

20. The MME transmits a TAU Accept message to the UE.

The TAU Accept message may include GUTI, TAI list, EPS bearer status,NAS sequence number, NAS-MAC, ISR activated, IMS Voice over PS sessionsupported, Emergency Service Support indicator, LCS Support Indication,and Supported Network Behavior.

When the active flag is set, the MME may provide a Handover RestrictionList to the eNB. When the active flag is set in the TAU Request message,the user plane setup procedure is activated with the TAU Accept message.When this procedure is a TAU procedure without the MME change and the DLData Buffer Expiration Time in the MM context for the UE in the MME doesnot expire or when this procedure is a TAU procedure accompanied by theMME change and the old MME/old S4-SGSN indicates the Buffered DL DataWaiting, the user plane setup procedure is activated even if the MMEdoes not receive the active flag in the TAU Request message. Even if thenew MME does not receive the active flag in the TAU Request message whenthe new MME receives the Downlink Data Notification message or anydownlink signaling message while the UE is still connected, the userplane setup procedure may be activated.

In the case of the UE using CIoT EPS Optimization having no active PDNconnection, the EPS bearer status is not included in the TAU requestmessage.

The MME indicates the CIoT EPS Optimization supported and preferred bythe MME in Supported Network Behavior information.

21. When the GUTI is changed, the UE acknowledges the received messageby transmitting the TAU Complete message to the MME.

When the active flag is not set in the TAU Request message and the TAUis not initiated in the ECM-CONNECTED state, the MME releases thesignaling connection with the UE according to the S1 release procedure.

After the new MME performs the security function or after the new MMEwaits for completion of the TAU procedure, the new MME may initiateestablishment of E-UTRAN Radio Access Bearer (E-RAB). For the UE, theE-RAB establishment may occur at any time after the TAU request istransmitted.

Hereinafter, the operations in the UE and the MME during the TAUprocedure will be described in more detail.

FIG. 17 illustrates a tracking area update procedure in a wirelesscommunication system to which the present invention may be applied.

Referring to FIG. 17, the UE in the EMM-REGISTERED state initiates theTAU procedure by transmitting a TRACKING AREA UPDATE REQUEST message tothe MME in the following cases (S1701 a and S1701 b):

a) when it is detected that the UE enters a TA that is not in the listof TAs that are previously registered in the MME (when the UE is not setto “AttachWithIMSI” or when the UE enters the TA in a new PLMN which isneither a registered PLMN nor a PLMN in an equivalent PLMN list);

b) when a periodic tracking area updating timer T3412 expires;

c) when the UE enters an EMM-REGISTERED.NORMAL-SERVICE (selected by theUE as a basic substate when the UE enters the EMM-REGISTERED state) anda Temporary Identity used in Next update (TIN) indicates “P-TMSI”;

d) when the UE performs an inter-system change from the S101 mode (i.e.,using the S101 reference point) to the S1 mode (i.e., use of the S1interface between the access network and the core network) and the userdata is pending;

e) when the UE receives an indication from the lower layer that the RRCconnection is released due to “load balancing TAU required”;

f) when the UE locally deactivates the EPS bearer context(s) in anEMM-REGISTERED.NO-CELL-AVAILABLE state (when the UE is out of E-UTRANcoverage or a Power Saving Mode in the UE is activated) and returns tothe EMM-REGISTERED.NORMAL-SERVICE state;

g) when UE network capability information or MS network capabilityinformation or both information is changed;

h) when the UE changes a UE specific DRX parameter;

i) when the UE receives an indication of “RRC Connection failure” fromthe lower layer and there is no pending signaling or user data (i.e.,the lower layer requests NAS signaling connection recovery);

j) when the UE enters the S1 mode after 1× Circuit Switched (CS)fallback or 1× Single Radio Voice Call Continuity (SRVCC);

k) when the UE selects a CSG cell having a CSG identity not included ina UE's allowed CSG list or a UE's operator CSG list and an associatedPLMN identity due to passive CSG selection;

l) when the UE reselects the E-UTRAN cell while the UE is in a GPRSREADY state or a PMM-CONNECTED mode;

m) when UE supports SRVCC to GERAN or UTRAN or Single Radio Video CallContinuity (vSRVCC) to UTRAN and changes mobile station classmark 2 orsupported codec or UE supports SRVCC to GERAN and changes mobile stationclassmark 3;

n) when the UE changes the radio capability of GERAN or cdma2000 or boththe radio capabilities;

o) when utilization setting of the UE or the voice domain preference forE-UTRAN is changed in the UE;

p) when the UE activates mobility management for IMS voice terminationand the TIN indicates “RAT-related TMSI”;

q) when the UE performs the intersystem change from an A/Gb mode to theS1 mode and the TIN indicates the “RAT-related TMSI”, but when the UE isrequired to perform the TAU for the IMS voice termination;

r) when a timer T3346 (mobility management back-off timer) is driven andthe UE is in an EMM-REGISTERED.ATTEMPTING-TO-UPDATE state (TAU orcombined TAU procedure is unsuccessful due to loss of the response fromthe network), a paging indication using the S-TMSI is received;

s) when the UE needs to update the network using the EPS bearer contextstate due to local de-activation of the EPS bearer context(s);

t) when the UE needs to request use of PSM or needs to stop using PSM;

t) when the UE needs to request use of extended DRX (eDRX) or needs tostop using the eDRX;

v) when an eDRX usage condition is changed in the UE and differentextended DRX parameters are requested;

w) when the PSM usage condition is changed in the UE and a differenttimer T3412 (periodic TAU timer) value or a different timer T3324(active timer) value is requested;

x) when the UE needs to request the CIoT EPS optimization;

In all cases except subclause b above, the UE sets an EPS update type IEin the TRACKING AREA UPDATE REQUEST message to “TA updating”. In thecase of subclause b, the UE sets the EPS update type IE to “periodicupdating”.

In the case of subclause n, the UE encapsulates a UE radio capabilityinformation update needed IE in the TRACKING AREA UPDATE REQUESTmessage.

In the case of subclause 1, when the TIN indicates the “RAT-relatedTMSI”, the UE sets the TIN to “P-TMSI” before initiating the TAUprocedure.

In the case of subclause r, an “active” flag in the EPS update type IEis set to 1.

When the UE has no established PDN connection, the “active” flag in theEPS update type IE is set to 0.

That is, when the UE is thus in an EMM-REGISTERED.ATTEMPTING-TO-UPDATEstate due to a failure in successfully performing the TAU and the likeand receives MT paging from the network while a mobility management (MM)back-off timer T3346 is driven, the UE may respond to the paging throughthe TAU. In this case, the UE particularly sets the “active” flag to 1to transmit the TAU request message to the MME.

When the UE initiates the TAU procedure, if the UE has established PDNconnection(s) and pending uplink user data or has uplink signaling notassociated with the TAU procedure, the UE may set the “active” flag inthe TRACKING AREA UPDATE REQUEST in order to indicate the request toestablish the user plane to the network and to maintain the NASsignaling connection after completion of the TAU procedure.

When the TAU request is accepted by the network, the MME transmits aTRACKING AREA UPDATE ACCEPT message to the UE (S1702 a).

The MME may encapsulate a new TAI list for the UE in the TRACKING AREAUPDATE ACCEPT.

Further, when the MME assigns new GUTI to the UE, the GUTI is includedin the TRACKING AREA UPDATE ACCEPT message.

Further, during the TAU procedure without the “active” flag, when theMME locally deactivates the EPS bearer context(s) for any reason, theMME encapsulates an EPS bearer context status IE in the TRACKING AREAUPDATE ACCEPT message to inform the UE of the deactivated EPS bearercontext(s).

When the “active” flag is included in the TRACKING AREA UPDATE REQUESTmessage, the MME re-establishes the radio bearer and S1 bearer for allactive EPS bearer context(s).

When the “active” flag is not included in the TRACKING AREA UPDATEREQUEST message, the MME may re-establishes the radio bearer and S1bearer for all active EPS bearer context(s) due to downlink pending dataor downlink pending signaling.

When the TRACKING AREA UPDATE ACCEPT message includes the GUTI, the UEresponds to the MME with TRACKING AREA UPDATE COMPLETE in order toacknowledge the received GUTI (S1703 a).

When the TAU may not be accepted by the network, the MME transmits tothe UE a TRACKING AREA UPDATE REJECT message including an appropriateEMM cause value (S1702 b).

S1 Release Procedure

The S1 release procedure is used to release the logical S1-AP signalingconnection (via S1-MME) and all S1 bearer(s) (in S1-U) for the UE. Thisprocedure releases the S11-U bearer (except for buffering in the MME) inthe CP CIoT EPS Optimization instead of the S1-U bearer. This procedurechanges the UE and all UEs in the MME from ECM-CONNECTED to ECM-IDLE andall UE related context information is deleted in the eNB. When the S1-APsignaling connection is lost (for example, due to loss of signalingforwarding or the failure of the eNB or MME), the S1 release procedureis performed by the eNB and/or MME. The S1 release procedure isperformed locally by the eNB or by the MME and each node locallyperforms the operation without direct signaling between the eNB and theMME.

The S1 release procedure is initiated as one of the followings.

-   -   Cause initiated by the eNB: For example, Operations and        Maintenance (O & M) coordination, Unspecified Failure, User        Inactivity, Repeated RRC signaling integrity check failures RRC        signaling Integrity Check Failure, Release due to UE generated        signaling connection release, CS Fallback triggered, Inter-RAT        Redirection, etc.; or    -   Cause initiated by the MME: authentication failure, detach, not        allowed CSG cell (e.g., the CSG ID of the currently used CSG        cell expires or delete from subscription data), etc.

FIG. 18 is a diagram illustrating an S1 release procedure in a wirelesscommunication system to which the present invention may be applied.

1a. In a specific case, the eNB may release the signaling connection ofthe UE either before or at the same time as requesting the MME torelease the S1 context. For example, the eNB may initiate an RRCConnection Release for CS fallback by redirection.

1b. When the eNB detects that the signaling connection of the UE and allradio bearers for the UE need to be released, the eNB transmits an S1 UEContext Release Request message (including the cause) to the MME. Thecause indicates the reason for the release (for example, O & Mintervention, unspecified failure, user inactivity, repeated integritychecking failure, or release due to UE generated signaling connectionrelease).

Step 1 above is performed only in the S release procedure initiated bythe eNB and the S1 release procedure initiated by the MME is performedfrom step 2.

In the case of the CP EPS Optimization accompanied by data whilebuffering in the MME, steps 2 and 3 are skipped.

2. When the MME is buffering all S1-U bearer(s) for the UE or S-GW, theMME transmits a Release Access Bearers Request message (an AbnormalRelease of Radio Link Indication of the radio link) to the S-GW in orderto request the release of S11-U in the CP CIoT EPS Optimization. Themessage is triggered by the S1 Release Request message or another MMEevent from the eNB.

3. When the S-GW receives the release access bearers request message,the S-GW releases all eNB related information (i.e., address andTEID(s)) for the UE or MME TEID(s) related information in the CP CIoTEPS Optimization and responds to the MME with the Release Access BearersRelease message. Other elements of the S-GW context of the UE are notinfluenced. The S-GW maintains an S1-U configuration which the S-GWallocates to the bearer(s) of the UE.

4. The MME releases S1 by transmitting the S1 UE Context Release Commandmessage (including the cause) to the eNB.

5. When the RRC connection is not already released, the eNB transmitsthe RRC Connection Release message to the UE in Acknowledged Mode (AM).When the message is acknowledged by the UE, the eNB deletes the contextof the UE.

6. The eNB confirms the release of S1 by transmitting S1 UE ContextRelease Complete message (including ECGI and TAI) to the MME. At thesame time, the signaling connection between the MME and the eNB for theUE is released. This step is performed immediately after step 4 above.

The MME deletes any eNB related information (i.e., an eNB address usedfor the S1-MME, an MME UE S1 AP ID, and an eNB UE S1AP ID) from the MMEcontext of the UE, but holds remaining information (address and TEID(s))of the MME context of the UE including S1-U setting information of theS-GW.

Mobile Originated (MO) Data Control Method During TAU Procedure

When the UE initiates the TAU procedure, if the uplink data to betransmitted to the network is pending, the UE may set the active flag inthe TRACKING AREA UPDATE REQUEST message.

In this case, after the MME completes the TAU procedure (i.e., after theTRACKING AREA UPDATE ACCEPT message is transmitted to the UE), the userplane setup procedure is performed. In this case, during the TAUprocedure, the path (i.e., entities in the network for uplink datatransmission) for the uplink data transmission of the UE and the contextof the UE in the corresponding entity are determined, so that the UE maynot transmit the uplink data to the network during the TAU procedure andthe user plane setup procedure is performed after the TAU procedure iscompleted.

This is similarly even to the UE using the CIoT EPS Control PlaneOptimization.

At present, when the UE initiates the TAU procedure, if the UE haspending uplink data to be transmitted via the user plane, only anoperation of setting the active flag in the TRACKING AREA UPDATE REQUESTmessage is defined. Therefore, in the case of the UE using the CIoT EPSControl Plane Optimization, when the UE initiates the TAU procedure, ifthe UE has the pending uplink data to be transmitted via the controlplane, operations of the UE and the network (e.g., MME) need to bedefined.

1) Problem 1 (Uplink View when Reusing Active Flag)

As described above, when the current UE performs the TAU procedure inthe IDLE mode, if the NAS layer of the UE has buffered (i.e., pending)data in the UE at the time of transmitting the TRACKING AREA UPDATEREQUEST message, the active flag in the TRACKING AREA UPDATE REQUESTmessage may be set.

Therefore, when the active flag is set after the TAU procedure isperformed, the MME may set up the DRB by performing the Initial Contextsetup instead of performing the S1 release procedure after transmittingthe TRACKING AREA UPDATE ACCEPT message to the UE. That is, when theactive flag is set in the TAU Request message, the user plane setupprocedure is activated with the TRACKING AREA UPDATE ACCEPT message. Inother words, when the active flag is included in the TRACKING AREAUPDATE REQUEST message, the MME re-establishes the radio bearer (i.e.,DRB) and S1 bearer for all active EPS bearer context(s).

Since the DRB and the S bearer are established as described above, theUE may transmit the uplink data to be transmitted to the network.

In this case, when data transmission/reception with the UE is notdetected, the eNB may request the MME to release the S1 and terminatethe connection.

On the contrary, when the current UE uses the CIoT EPS Control PlaneOptimization, the DRB bearer and the S1 bearer may not be used for datatransmission/reception, and this will be described with reference to thefollowing drawings.

FIG. 19 is a diagram illustrating control plane optimization and userplane optimization in a wireless communication system to which thepresent invention may be applied.

Referring to FIG. 19, when the current UE uses the User Plane CIoT EPSOptimization, uplink/downlink data transmission and reception may beperformed between the UE and the network (for example, P-GW/S-GW) byusing a DRB↔S1-U↔SGi path.

On the contrary, when the current UE uses the CIoT EPS Control PlaneOptimization, the uplink/downlink data transmission and reception may beperformed between the UE and the network (for example, P-GW/S-GW) byusing a SRB↔S1-MME↔S11-U path instead of a DRB↔S1-U path using ASsecurity in the related art. Alternatively, the uplink/downlink datatransmission and reception may be performed with an application server(AS) via the SCEF.

As described above, when the UE sets the active flag in an ATTACHREQUEST message (or a TRACKING AREA UPDATE REQUEST message) bydetermining MO data transmission, the MME performs an initial contextsetup to activate the user plane.

In this case, even if the UE selects Control Plane CIoT EPS Optimizationfor MO data transmission, when the active flag in the TRACKING AREAUPDATE REQUEST message is set, resource waste and unnecessary signalingat the UE occur due to an unnecessary E-RAB setup operation such assetting up the AS security or the like.

More specifically, when the UE uses only the Control Plane CIoT EPSOptimization, even if the UE desires to transmit uplink data in thecontrol plane, if the active flag in the TRACKING AREA UPDATE REQUESTmessage is set, as the radio bearer (i.e. DRB) and the S1 bearer areunnecessarily re-established, waste of resources occurs and asunnecessary signaling with the UE occurs, power of the UE is consumed.

Further, when the UE uses both the Control Plane CIoT EPS Optimizationand the User Plane CIoT EPS Optimization, even if the UE desires totransmit the uplink data in the control plane, if the active flag in theTRACKING AREA UPDATE REQUEST message is set, similarly thereas the radiobearer (i.e. DRB) and the S1 bearer are unnecessarily re-established,waste of resources occurs and as unnecessary signaling with the UEoccurs, power of the UE is consumed. Further, when the DRB isestablished, the RAI may not be applied, so that the S1 release isdelayed. In addition, when the corresponding UE is not an NB-IoT UE(i.e., non NB-IoT UE), AS the DRB is established, the base station maytrigger a measurement report to the UE, thereby consuming the power ofthe UE.

On the contrary, when the UE determines that the DRB setup is notrequired (i.e., when the UE desires to transmit the uplink data in thecontrol plane) and does not encapsulate the active flag in the ATTACHREQUEST message (or TRACKING AREA UPDATE REQUEST message), the MMEperforms the S release procedure (see FIG. 18 above) by the operations(see FIG. 14 above) (10 steps in FIG. 15 and 21 steps in FIG. 16) of 21steps of the TAU procedure.

Step 21 in FIG. 14, step 10 in FIG. 15, and step 21 in FIG. 16 will bedescribed again.

-   -   When the active flag is not set in the TRACKING AREA UPDATE        REQUEST message and the TAU is not initiated in the        ECM-CONNECTED state, the MME releases the signaling connection        with the UE according to the S1 release procedure (see FIG. 18        above).

Accordingly, the signaling connection is released without a margin forthe UE to transmit the MO data through the SRB. In this case, there areinconvenience and inefficiency that the UE needs to establish the RRCconnection again.

2) Problem 2 (Downlink View when Reusing Active Flag)

In addition, when MO data (i.e., uplink data) to be transmitted throughthe SRB (i.e., via the control plane) is pending when the UE performsthe TAU procedure, an operation of whether the active flag is to set isnot defined together with the TRACKING AREA UPDATE REQUEST message.

As a result, while the UE is using the Control Plane CIoT EPSOptimization, the UE may not successfully perform the TAU and is in theEMM-REGISTERED.ATTEMPTING-TO-UPDATE state. When the UE receives the MTpaging while the MM back-off timer T3346 is being driven, the UE cannotbut transmit the TRACKING AREA UPDATE REQUEST message to the MME bysetting the active flag even when intending to receive the MT datathrough the SRB or being capable of receiving the MT data only throughthe SRB.

This case may correspond to a situation in which an impossible DRB setupis requested or an unnecessary DRB setup is requested, therebyincreasing the power consumption of the UE and wasting networkresources.

Accordingly, the present invention proposes a method in which user planeactivation/setup (i.e., DRB and S1 bearer setup) is not required duringthe TAU procedure while the UE uses the Control Plane CIoT EPSOptimization, but the UE may transmit the MO data without causing the S1release immediately after the TAU procedure is completed when the datato be transmitted is pending via the control plane.

Prior to the description of the present invention, terms used in thisspecification will be described below.

-   -   Dedicated bearer: An EPS bearer associated with an uplink packet        filter(s) in the UE and a downlink packet filter(s) in a P-GW.        Here, only a specific packet matches a filter(s).    -   Default bearer: An EPS bearer established as every new PDN        connection. A context of the default bearer is maintained during        a lifetime of the PDN connection.    -   EPS Mobility Management (EMM)-null (EMM-NULL) state: An EPS        service in the UE is deactivated. No EPS mobility management        function is also performed.    -   EMM-DEREGISTERED state: In an EMM-DEREGISTERED state, an EMM        context is not established and a UE position is not notified to        the MME. Therefore, the UE is unreachable by the MME. In order        to establish the EMM context, the UE needs to start an attach        procedure or combined attach procedure.    -   EMM-REGISTERED state: In an EMM-REGISTERED state, the EMM        context in the UE is established and a default EPS bearer        context is activated. When the UE is in an EMM-IDLE mode, the UE        position is notified to the MME with accuracy of a list of TAs        including a specific number of a TA. The UE may start        transmission and reception of user data and signaling        information. Further, a TAU or a combined TAU procedure is        performed.    -   EMM-CONNECTED mode: When an NAS signaling connection is        established between the UE and the network, the UE is in the        EMM-CONNECTED mode. A term of EMM-CONNECTED may be referred to        as a term of the EMM-CONNECTED state.    -   EMM-IDLE mode: When the NAS signaling connection does not exist        between the UE and the network or RRC connection suspend is        indicated by the lower layer, the UE is in the EMM-IDLE mode. A        term of EMM-IDLE may be referred to as a term of the EMM-IDLE        state.    -   EMM context: When the attach procedure is successfully        completed, the EMM context is established in the UE and the MME.    -   Control plane CIoT EPS optimization: Signaling optimization to        enable efficient transport of user data (IP, non-IP or SMS)        through a control plane via the MME. The control plane CIoT EPS        optimization may selectively include header compression of IP        data.    -   User Plane CIoT EPS optimization: Signaling optimization to        enable efficient transport of user data (IP or non-IP) through a        user plane    -   EPS service(s): Service(s) provided by the PS domain    -   NAS signaling connection: Peer-to-peer S2 mode connection        between the UE and the MME. The NAS signaling connection is        configured by concatenation of an RRC connection via an LTE-Uu        interface and an S1AP connection via an S1 interface.    -   UE using EPS services with control plane CIoT EPS optimization:        UE attached for EPS service accompanying control plane CIOT EPS        optimization accepted by the network

1) First Embodiment: Additional Indication Setting

In the first embodiment of the present invention, when the MO data to betransmitted through the SRB (i.e., control plane) is generated duringthe TAU procedure, two following options are available according towhether to setting the active flag together with the TRACKING AREAUPDATE REQUEST message.

-   -   Option 1: According to Option 1, it is proposed that an        additional indication flag is defined.

When the UE determines that there is buffered MO data while performingthe TAU and the corresponding MO data transmission does not require theAS security setup, i.e., user plane setup (e.g., DRB and S1 bearersetup), a flag (for example, a new flag) for distinguishing it from anexisting active flag may be additionally defined.

Hereinafter, in the description of the present invention, the meaningthat the active flag and/or the new flag are included in the TRACKINGAREA UPDATE REQUEST message may be interpreted to have the same meaningas the active flag and/or the new flag are set.

Hereinafter, the active flag and/or the new flag are set for convenienceof description of the present invention, which means that the value ofthe active flag and/or the new flag is set to ‘1’ unless otherwisenoted. In this case, the fact that the active flag and/or the new flagare not set may mean that the value of the active flag and/or the newflag is set to ‘0’.

Also, in this specification, the new flag newly defined according to thepresent invention may be referred to as an additional indication flag, acontrol plane (CP) active flag, a signaling active flag, a first activeflag, and the like. Further, the existing defined active flag (i.e., theflag set when there is pending user data to be transmitted via the userplane at the time of initiating the TAU) may be referred to as an activeflag or a second active flag.

That is, when the user plane setup (i.e., DRB and S1 bearer setup) isnot required but the MO data transmission is required via the controlplane (i.e., SRB) and the delay of S1 release is required, the UE maytransmit the TAU request message including an indication (i.e., a newflag) that requests the corresponding operation in addition to theactive flag. Here, the delay of the release of S means that theinitiation of the S release procedure (FIG. 18) is delayed, and the RRCconnection and the S1AP connection are released according to the Srelease procedure, and as a result, the delay of the S release may meanthe delay of the release of the NAS signaling connection.

As a result, the new flag may indicate a request to maintain the NASsignaling connection after completion of the TAU procedure.

In other words, when the UE uses the Control Plane CIoT EPS optimization(i.e., signaling optimization to enable the delivery of the user datathrough the control plane via the MME), and the UE does not have pendinguser data to be transmitted through the user plane and has pending userdata to be transmitted through the control plane via the MME, the newflag may be set in the TRACKING AREA UPDATE REQUEST message.

When the corresponding indication (i.e., new flag) in the TRACKING AREAUPDATE REQUEST is set or included, the MME does not perform the S1release procedure even after transmitting the TRACKING AREA UPDATEACCEPT message to the UE and may maintain the NAS signaling connections(i.e., RRC connection and S1AP connection) for a predetermined time.

In other words, when the active flag is not set in the received TRACKINGAREA UPDATE REQUEST message and the MME receives the indication (i.e.,new flag) that transmission of the MO data without the AS security setup(i.e., user plane setup) is required, the MME may perform the delayed S1release or may not perform the S1 release.

That is, when the corresponding indication (i.e., new flag) is included(set) in the TRACKING AREA UPDATE REQUEST, the MME may delay the releaseof the NAS signaling connections (i.e., RRC connection and S1APconnection) after the TAU procedure is completed or may not release theNAS signaling connection (immediately).

When the MME does not perform the S1 release procedure, the eNB maytrigger the S1 release procedure by the inactivity of the UE.

As another embodiment of Option 1, a flag/indication used for anotherpurpose in the related art may be included in the TRACKING AREA UPDATEREQUEST message instead of defining the new flag.

For example, the Release Assistant Indication (RAI) introduced in theCIoT EPS Optimization may be used. The RAI includes quick connectionrelease information for data over the NAS transmitted by the UE, but theRAI is included in the TRACKING AREA UPDATE REQUEST message, so that itmay be implicitly notified to the network that the data transmission isdesired not through the user plane path but by the control plane CIoTEPS optimization (i.e., Data over NAS) after the TAU procedure isterminated. In this case, when the RAI is included in the TRACKING AREAUPDATE REQUEST message transmitted from the UE, the MME may recognizethat there is pending data using the data over the NAS for the UE. Inaddition, accordingly, the MME may not perform the S1 release even afterthe TAU procedure is successfully performed.

As yet another example, the UE may set the RAI value to 00 (no availableinformation).

Alternatively, regardless of the information depending on the RAI valueas shown in Table 3 above, when the RAI is included in the TRACKING AREAUPDATE REQUEST message, the MME may regard that the data over the NAS ispending.

The MME may then determine whether to release the S after receiving thedata over the uplink NAS based on the RAI value included in the dataincluded for the UE to transmit the data over the NAS.

-   -   Option 2: The additionally defined new flag proposed in Option 1        above may be defined for the purpose of meaning the Control        Plane CIoT EPS Optimization.

That is, when the active flag is set in the TRACKING AREA UPDATE REQUESTand the new flag including the meaning of using the Control Plane CIoTEPS Optimization is additionally set, the MME may delay the S1 releaseor may not initiate the S1 release instead of not performing the initialcontext setup even though the active flag is set.

However, if the active flag is set but the new flag is not set or if theactive flag is set but does not mean the use of the Control Plane CIoTEPS Optimization, the MME performs the initial context setup toestablish the DRB (i.e., user plane activation).

In addition, although the received active flag and a combination of thenew flag/indication exist in the MO data, the MME may perform theinitial context setup when the DRB setup is required by the amount ofdata buffered to the S-GW and a policy in the direction of the MT eventhough performing the initial context setup of requesting the DRB setupis not requested.

FIG. 20 illustrates a tracking area update procedure according to anembodiment of the present invention.

Although steps 4 to 20 and 21 of the tracking area update procedure inFIG. 20 illustrate the steps in FIG. 14 above, the present invention maybe equally applied to the tracking area update procedure of FIG. 15above and the tracking area update procedure of FIG. 16.

That is, when the present invention is applied to the tracking areaupdate procedure according to FIG. 15, steps 4 to 20 of the trackingarea update procedure in FIG. 20 may be replaced with steps 4 to 10 (TAUAccept) of FIG. 15, and step 21 of the tracking area update procedure inFIG. 20 may be replaced with step 10 (TAU Complete) of FIG. 15.

In addition, when the present invention is applied to the tracking areaupdate procedure according to FIG. 16, steps 4 to 20 of the trackingarea update procedure in FIG. 20 may be replaced with steps 4 to 20 ofFIG. 15, and step 21 of the tracking area update procedure in FIG. 20may be replaced with step 21 of FIG. 16.

Step 1: When the TAU procedure is triggered, the UE determines whetherthere is buffering (or pending) MO data. At this time, the UE maydetermine whether the MO data to be transmitted via a user plane ispending and/or the MO data to be transmitted via a control plane ispending.

In this case, when the control plane CIoT EPS optimization is applicable(for example, when the control plane CIoT EPS optimization is fixed orwhen user plane/control plane CIoT EPS optimization both areapplicable), the corresponding UE sets a new flag that DRB setup (thatis, user plane setup) is not required to transmit a TRACKING AREA UPDATEREQUEST message to the MME.

Here, the new flag may be set by the two options described above.

Step 2: The UE transmits a TRACKING AREA UPDATE REQUEST messageincluding the new flag to the MME.

Steps 4 to 20: An existing tracking area procedure is performed. Asdescribed above, steps 4 to 20 of FIG. 14, steps 4 to 10 (TAU Accept) ofFIG. 15, or steps 4 to 20 of FIG. 14 may be performed. A detaileddescription thereof will be omitted.

At this time, if the TRACKING AREA UPDATE REQUEST message transmittedfrom the UE is accepted by the network in the last step (i.e., step 20in FIG. 14, step 10 in FIG. 15, or step 20 in FIG. 16), the MMEtransmits a TRACKING AREA UPDATE ACCEPT message to the UE.

Step 21: The MME determines whether initial context setup is performed(i.e., whether the user plane is set up) and whether S1 release isperformed (i.e., whether the NAS signaling connection is released) bythe combination of the new flag and the active flag.

If the active flag is included in the TRACKING AREA UPDATE REQUESTmessage and the control plane CIoT EPS optimization is not used by theMME, the MME may re-establish the radio bearer(s) and S1 bearer(s) forall active EPS bearer contexts.

Alternatively, if the active flag is included in the TRACKING AREAUPDATE REQUEST message and the control plane CIoT EPS optimization isused by the MME, the MME may re-establish the radio bearer(s) and S1bearer(s) for all active EPS bearer contexts associated with establishedPDN connection without indication (i.e., CP only indication) of only thecontrol plane.

If it is determined that the initial context setup is not required, butthe MO transmission (MME terminal reception) by the CIoT EPS controlplane optimization of the UE is required, the S1 release may be delayedand performed, or the MME end may not perform the S1 release and the eNBend may wait for performing the S1 release.

In other words, if the new flag is included in the TRACKING AREA UPDATEREQUEST message and the control plane CIoT EPS optimization is used bythe MME, the MME may not release (immediately) the NAS signalingconnection after completion of the TAU procedure.

For example, if a GUTI is included in a TRACKING AREA UPDATE ACCEPTmessage, the UE may acknowledge the received message by transmitting aTRACKING AREA UPDATE COMPLETE message to the MME.

If the active flag (or both the active flag and the new flag) is not setin the TRACKING AREA UPDATE REQUEST message and the TAU procedure is notinitiated in an ECM-CONNECTED state, the MME may release the signalingconnection of the UE according to the procedure of FIG. 18 above. In thecase of the UE using the control plane CIoT EPS optimization, if the newflag (or CP active flag) is set, the MME may not immediately release theNAS signaling connection to the UE after the TAU procedure is completed.

As another example, if the GUTI is included in the TRACKING AREA UPDATEACCEPT message, the UE may acknowledge the received message bytransmitting the TRACKING AREA UPDATE COMPLETE message to the MME.

If the active flag (or both the active flag and the new flag) is not setin the TRACKING AREA UPDATE REQUEST message and the TAU procedure is notinitiated in an ECM-CONNECTED state, the MME may release the signalingconnection of the UE according to the procedure of FIG. 18 above. In thecase of the UE using the control plane CIoT EPS optimization, if the newflag (or CP active flag) is not set in the TRACKING AREA UPDATE REQUESTmessage, the MME may (immediately) release the NAS signaling connectionto the UE after the TAU procedure is completed.

Hereinafter, the operations of the UE and the MME in the tracking areaupdate procedure will be described in more detail with reference to thedrawings.

FIG. 21 illustrates a tracking area update procedure according to anembodiment of the present invention.

Referring to FIG. 21, the UE transmits a TRACKING AREA UPDATE REQUESTmessage to the MME (S2101).

That is, if the triggering condition of the TAU procedure describedabove is satisfied, the UE initiates the TAU procedure by transmittingthe TRACKING AREA UPDATE REQUEST message to the MME.

At this time, according to whether the UE uses control plane CIoT EPSoptimization and whether the UE has user data to be transmitted via acontrol plane, whether a first active flag (i.e., a new flag, a CPactive flag, and a signaling active flag) is set in the TRACKING AREAUPDATE REQUEST message may be determined.

For example, when the UE uses the control plane CIoT EPS optimization(i.e., signaling optimization to enable transmission of user datathrough the control plane via the MME) and the UE has pending user datato be transmitted via the control plane through the MME, not pendinguser data to be transmitted via the user plane, the first active flag(i.e., a new flag, a CP active flag, and a signaling active flag) may beset in the TRACKING AREA UPDATE REQUEST message.

Further, when the UE uses the control plane CIoT EPS optimization (i.e.,signaling optimization to enable transmission of user data through thecontrol plane via the MME) and the UE has uplink signaling notassociated with the TAU procedure (e.g., a PDN connectivity request forrequesting additional PDN connection including default bearer allocationafter the TAU procedure by the UE, request bearer resource modificationfor requesting modification of bearer resources for a single trafficflow combined with a specific QoS requirement after the TAU procedure bythe UE, or the like), the first active flag (i.e., a new flag, a CPactive flag, and a signaling active flag) may be set in the TRACKINGAREA UPDATE REQUEST message.

At this time, the first active flag may indicate a request to maintainthe NAS signaling connection between the UE and the MME after completionof the TAU procedure. In other words, the first active flag is a requestfor maintaining NAS signaling connection after the TAU procedure iscompleted by the UE using the control plane CIoT EPS optimization, sothat the UE transfers pending data or NAS signaling using data transferin the control plane CIoT EPS optimization.

The MME transmits a TRACKING AREA UPDATE ACCEPT message to the UE(S2102).

That is, if the TRACKING AREA UPDATE REQUEST is accepted by the network,the MME transmits a TRACKING AREA UPDATE ACCEPT message to the UE.

At this time, the MME operation after the completion of the TAUprocedure of the MME (for example, the operation after the transmissionof the TRACKING AREA UPDATE ACCEPT message) may be determined dependingon whether the first active flag is set in the TRACKING AREA UPDATEREQUEST.

For example, if the first active flag is included in the TRACKING AREAUPDATE REQUEST message, the MME may not (immediately) release the NASsignaling connection after the completion of the TAU procedure. In otherwords, in the case of the UE using the control plane CIoT EPSoptimization, if the first active flag is set in the TRACKING AREAUPDATE REQUEST message, the MME may not release the NAS signalingconnection (immediately) after the TAU procedure is completed.

Further, if the first active flag is included in the TRACKING AREAUPDATE REQUEST message and the control plane CIoT EPS optimization isused by the MME, the MME may not release (immediately) the NAS signalingconnection after completion of the TAU procedure.

Also, if the first active flag is not included (set) in the TRACKINGAREA UPDATE REQUEST message, the MME may release the NAS signalingconnection of the UE according to the procedure of FIG. 18 above.

Meanwhile, when the UE receives the TRACKING AREA UPDATE ACCEPT message,it is determined whether a predetermined timer (for example, a T3440timer) is driven according to whether the first active flag is set inthe TRACKING AREA UPDATE REQUEST message.

That is, if the UE does not set the first active flag in the TRACKINGAREA UPDATE REQUEST message, the UE starts a predefined timer (e.g., theT3440 timer).

In addition, when the corresponding timer (e.g., the T3440 timer)expires, the UE releases locally established NAS signaling connection.

As described above, the MME may determine a user plane setup (i.e.,radio bearer and S1 bearer setup) and/or the NAS signaling disconnectionby combining the first active flag (i.e., a new flag, a CP active flag,and a signaling active flag) and a second active flag (i.e., a existingdefined active flag).

Referring back to FIG. 21, the UE transmits a TRACKING AREA UPDATEREQUEST message to the MME (S2101).

That is, if the triggering condition of the TAU procedure describedabove is satisfied, the UE initiates the TAU procedure by transmittingthe TRACKING AREA UPDATE REQUEST message to the MME.

At this time, according to whether the UE uses the control plane CIoTEPS optimization and whether the UE has user data to be transmitted viaany plane of user plane/control plane, whether the active flag or thefirst active flag (i.e., a new flag, a CP active flag, and a signalingactive flag) is set in the TRACKING AREA UPDATE REQUEST message may bedetermined.

More specifically, when the UE has pending user data to be transmittedvia the user plane (establishing the PDN connection(s)) when the UEinitiates the TAU procedure, or when the UE has the uplink signalingunrelated to the TAU procedure when not supporting the control planeCIoT EPS optimization, the UE may set the second active flag (i.e., theexisting defined active flag) in the TRACKING AREA UPDATE REQUESTmessage.

The second active flag (i.e., the existing defined active flag) mayindicate the request of the establishment of the user plane and therequest for maintaining the NAS signaling after the completion of theTAU procedure to the network.

On the other hand, when the UE uses the control plane CIoT EPSoptimization and the UE has pending user data to be transmitted via thecontrol plane through the MME without pending user data to betransmitted via the user plane or has uplink signaling unrelated withthe TAU procedure, the first active flag may be set in the TRACKING AREAUPDATE REQUEST message.

The first active flag (i.e., the new flag, the CP active flag, and thesignaling active flag) may indicate a request for maintenance of the NASsignaling connection after completion of the TAU procedure. In otherwords, the first active flag is a request for maintaining the NASsignaling connection after the TAU procedure is completed by the UEusing the control plane CIoT EPS optimization, so that the UE transferspending data or NAS signaling using data transfer in the control planeCIoT EPS optimization.

The MME transmits a TRACKING AREA UPDATE ACCEPT message to the UE(S2102).

That is, if the TRACKING AREA UPDATE REQUEST is accepted by the network,the MME transmits a TRACKING AREA UPDATE ACCEPT message to the UE.

At this time, the MME operation after the completion of the TAUprocedure of the MME (for example, the operation after the transmissionof the TRACKING AREA UPDATE ACCEPT message) may be determined dependingon whether the second active flag is set or the first active flag is setin the TRACKING AREA UPDATE REQUEST.

If the second active flag is included in the TRACKING AREA UPDATEREQUEST message and the control plane CIoT EPS optimization is not usedby the MME, the MME may re-establish the radio bearer(s) and S1bearer(s) for all active EPS bearer contexts.

Alternatively, if the second active flag is included in the TRACKINGAREA UPDATE REQUEST message and the control plane CIoT EPS optimizationis used by the MME, the MME may re-establish the radio bearer(s) and S1bearer(s) for all active EPS bearer contexts associated with establishedPDN connection without indication (i.e., CP only indication) of only thecontrol plane.

Alternatively, if the first active flag is included in the TRACKING AREAUPDATE REQUEST message, the MME may not (immediately) release the NASsignaling connection after the completion of the TAU procedure. In otherwords, in the case of the UE using the control plane CIoT EPSoptimization, if the first active flag is set in the TRACKING AREAUPDATE REQUEST message, the MME may not release the NAS signalingconnection (immediately) after the TAU procedure is completed.

In other words, if the first active flag is included in the TRACKINGAREA UPDATE REQUEST message and the control plane CIoT EPS optimizationis used by the MME, the MME may not (immediately) release the NASsignaling connection after completion of the TAU procedure.

If the second active flag (or both the second active flag and the firstactive flag) is not set in the TRACKING AREA UPDATE REQUEST message andthe TAU procedure is not initiated in an ECM-CONNECTED state, the MMEmay release the signaling connection of the UE according to theprocedure of FIG. 18 above.

Meanwhile, when the UE receives the TRACKING AREA UPDATE ACCEPT message,it is determined whether a predetermined timer (e.g., a T3440 timer) isdriven according to whether the second active flag and/or the firstactive flag are/is set in the TRACKING AREA UPDATE REQUEST message.

That is, if the UE does not set the second active flag in the TRACKINGAREA UPDATE REQUEST message, the UE starts the predefined timer (e.g.,the T3440 timer). That is, if the UE does not set the first active flagin the TRACKING AREA UPDATE REQUEST message, the UE starts thepredefined timer (e.g., the T3440 timer).

In addition, when the corresponding timer (e.g., the T3440 timer)expires, the UE releases locally established NAS signaling connection.

2) Example 2: MME Operation when Transmitting TAU Request Messagewithout Setting Active Flag

As described above, currently, when the active flag is not set in theTRACKING AREA UPDATE REQUEST message and the TAU is not initiated in theECM-CONNECTED state, the MME releases the signaling connection with theUE according to the S1 release procedure (see FIG. 18 above).

On the other hand, according to the present embodiment, when the UEinitiates the TAU procedure, if the uplink data to be transmitted to thenetwork via the control plane is pending, the active flag may not be setin the TRACKING AREA UPDATE REQUEST message.

That is, according to the present embodiment, the UE may operate asfollows.

-   -   If MO data to be transmitted through the SRB (i.e., through the        control plane) is pending when the UE performs the TAU        procedure, the UE does not set the active flag and transmits        only the TRACKING AREA UPDATE REQUEST message to the MME.    -   If the MO data to be transmitted through the DRB (i.e., through        the user plane) is pending when the UE performs the TAU        procedure, the UE sets the active flag and transmits the active        flag to the MME together with the TRACKING AREA UPDATE REQUEST        message.    -   If the MO data to be transmitted is not generated when the UE        performs the TAU procedure, the UE does not set the active flag        and transmits only the TRACKING AREA UPDATE REQUEST message to        the MME.

According to the present embodiment, even if the MME receives only theTRACKING AREA UPDATE REQUEST message from the UE without setting theactive flag, when the MME recognizes that the corresponding UE uses thecontrol plane CIoT EPS optimization (i.e., when the correspondingconnection uses only the control plane CIoT EPS optimization, uses boththe control plane CIoT EPS optimization and the user plane CIoT EPSoptimization, or the connection for SMS transmission), the MME may delaythe S release procedure (see FIG. 18 above), or the MME may not initiatethe S release procedure (see FIG. 18 above).

That is, the MME may provide a time margin for a predetermined period oftime so that the UE may transmit uplink data to the network via thecontrol plane.

According to the present embodiment, there is an advantage that there isno need to define a new flag. However, since this is performedirrespective of whether the uplink data to be transmitted to the UE viathe control plane is pending, there is a disadvantage in that therelease of the signaling connection is delayed even if there is nouplink data to be transmitted by the UE. In addition, since thesignaling connection is maintained for a certain period of time on theUE side, power consumption of the UE is increased.

3) Example 3

When the UE applies the user plane CIoT EPS optimization, the MMErecognizes that the ECM-IDLE mode conversion from the ECM-CONNECTED ofthe UE is previously performed by the RRC suspend procedure (i.e.,recognizes that the UE state is suspended) and recognizes that theresume procedure has been successfully performed in the UE and the DRBhas been set up (i.e., the MME receives the S1-AP UE context resumerequest from the eNB (See Section 5.3.5A of 3GPP TS 23.401)), even ifthe UE does not include the active flag in the ATTACH REQUEST/TRACKINGAREA UPDATE REQUEST, the operation of step 21 of the TAU procedure (seeFIG. 14 above) (step 10 in FIG. 15, step 21 in FIG. 16) may not beperformed. Then, the connection suspend procedure may be started by aninactivity timer in the eNB.

When it is determined that the connection is suspended (i.e., theECM-IDLE mode conversion from the previous ECM-CONNECTED is performed inthe connection suspend procedure and the UE has the AS context), thereis MO data to be transmitted by the UE when the TAU is performed, andthe DRB setup is required, the UE still includes (sets) the active flagin the TRACKING AREA UPDATE REQUEST message.

However, even if the active flag is set, the MME may not perform anadditional user plane setup (i.e., an initial context setup procedure)if the resume procedure is successfully performed.

At this time, if it is determined that the resume procedure has not beensuccessfully performed and the active flag is set in the TRACKING AREAUPDATE REQUEST message of the UE, the MME may perform a user plane setup(i.e., an initial context setup procedure) so that the update data maybe transmitted.

4) Example 4: Setting of New Flag in MT Paging

With respect to the problem 2 described above, the UE may correspond tothe following conditions.

i) The UE does not successfully perform the TAU procedure and the likeand is in the EMM-REGISTERED.ATTEMPTING-TO-UPDATE state.

ii) The MM backoff timer, T3346, is running.

iii) The UE receives MT paging in a situation of satisfying i) and ii).

In this case, the UE may respond to the paging by initiating the TAUprocedure.

At this time, if the UE is configured to use only the control plane CIoTEPS optimization (‘control plane only’ indication), or if the UE has thecapability to receive data through SRB and desires to receive the datathrough the SRB, the UE may transmit a TRACKING AREA UPDATE REQUESTmessage to the MME by setting a new flag defined in Example 1) insteadof the existing active flag.

The network may operate as follows according to the flag setting whenthe UE which has transmitted the paging above responds with a TRACKINGAREA UPDATE REQUEST message as the response message.

If the new flag is set in the TRACKING AREA UPDATE REQUEST message, thenetwork may not immediately release the NAS signaling connection (i.e.,perform the S1 release procedure) or maintain the NAS signalingconnection even after the TAU completion.

If the UE has only the capability to transmit the data to the SRB or isconfigured to CP only, the network needs to transmit the MT data to theSRB. Otherwise, the network may determine whether to transmit MT data tothe DRB or SRB by considering the policy of the provider, the resourcesituation at the time, and the characteristics of the MT data.

The operation of transmitting the data to the DRB is the same as theoperation when the active flag is set in the conventional TRACKING AREAUPDATE REQUEST message.

On the other hand, the operation of transmitting the data to the SRB mayfollow the operation when the DSR for MT paging (piggybacking andtransmitting the user data in the ESM data transport message) isreceived.

For example, the TAU procedure triggering conditions and operations maybe defined as follows.

The UE in the EMM-REGISTERED state initiates the TAU procedure bytransmitting the TRACKING AREA UPDATE REQUEST message to the MME.

r) If the timer T3346 is running and the UE is in theEMM-REGISTERED.ATTEMPTING-TO-UPDATE state, when receiving a pagingindication using the S-TMSI

That is, if the r condition is satisfied, the UE in the EMM-REGISTEREDstate transmits the TRACKING AREA UPDATE REQUEST message to the MME toinitiate the TAU procedure.

At this time, in the case of r, if the UE uses only the control planeCIoT EPS optimization or the UE does not have only the PDN connectionestablished with the “control plane only” indication, the active flagmay be set to 1 in the EPS update type IE. If the UE uses only thecontrol plane CIoT EPS optimization or the UE has only the PDNconnection established with the “control plane only” indication, the“control plane (CP) active flag may be set to 1 in the additional updatetype IE.

Alternatively, the TAU procedure triggering conditions and operationsmay be defined as follows.

The UE in the EMM-REGISTERED state initiates the TAU procedure bytransmitting the TRACKING AREA UPDATE REQUEST message to the MME.

r) If the timer T3346 is operating and the UE is in theEMM-REGISTERED.ATTEMPTING-TO-UPDATE state, when receiving a pagingindication using the S-TMSI

That is, if the r condition is satisfied, the UE in the EMM-REGISTEREDstate transmits the TRACKING AREA UPDATE REQUEST message to the MME toinitiate the TAU procedure.

At this time, in the case of r, if the UE is not using the EPSservice(s) using the control plane CIoT EPS optimization, the activeflag in the EPS update type IE is set to 1. If the UE is using the EPSservice(s) using the control plane CIoT EPS optimization, the “CPactive” flag in the additional update type IE may be set to 1.

Meanwhile, unlike the embodiment of the present invention describedabove, the first active flag (i.e., the new flag, the CP active flag,and the signaling active flag) may indicate whether maintenance of theNAS signaling connection is required after completion of the TAUprocedure.

For example, referring back to FIG. 21, if the maintenance of the NASsignaling connection between the UE and the MME is required after thecompletion of the TAU procedure, the UE may set the first active flag to‘1’ in step S2101.

On the other hand, if the maintenance of the NAS signaling connectionbetween the UE and the MME is not required after the completion of theTAU procedure, the UE may set the first active flag to ‘0’ in stepS2101.

According to Examples 1 and 4 above, while the UE is using the EPSservice(s) using the control plane CIoT EPS optimization, when the userdata to be transmitted through the control plane is pending when the UEinitiates the TAU procedure, setting of additional indications (i.e.,new flag or CP flag or signaling flag) needs to be added in the TRACKINGAREA UPDATE REQUEST message. The following method may be used.

-   -   Option 1) Use of Additional Update Type IE

The purpose of the Additional Update Type IE is to provide additionalinformation about the type of request for the combined attach or TAUprocedure.

The additional Update Type IE is coded as illustrated in FIG. 22 andTable 4 below.

The EPS update type IE is a type 1 IE.

FIG. 22 is a diagram illustrating an additional update type informationelement according to an embodiment of the present invention.

Referring to FIG. 22, the additional Update Type IE has a length of 1octet, 4 bits (i.e., bit 5 to bit 8) from the most significant bit (MSB)(alternatively, the left-most bit) indicates an additional update typeinformation element identifier (IEI), and the next 2 bits (i.e., bit 4and bit 3) indicates a preferred CIoT network behaviour (PNB-CIoT), thenext 1 bit (i.e., bit 2) indicates a NEW flag (i.e., first active flag),and the next 1 bit (i.e., bit 1) indicates an additional update typevalue (AUTV).

TABLE 4 Additional update type value (AUTV) (octet 1) Bit 1 0 Noadditional information. If received, it is interpreted as a request fora combined attach or a combined TAU. 1 SMS only Additional indicationsetting (octet 1) Bit 2 0 Immediately connection release aftercompletion of the procedure (i.e., release connection immediately aftercompletion of TAU, etc. like the operation in the related art) 1Presence of MO data (MO data over NAS) through NAS/Connectionretention/No DRB setup (do not release immediately after completion ofTAU, etc.) Preferred CIoT network behaviour (PNB-CIoT) (Octet 1) Bit 4 30 0 No additional information 0 1 Control-plane CIoT EPS optimization 10 User-plane EPS optimization 1 1 Reserved

Option 2) Use of EPS Update Type IE

The purpose of the EPS update type IE is to specify an area related withthe update procedure.

The EPS update type IE is coded as illustrated in FIG. 23 and Table 5below.

The EPS update type IE is a type 1 IE.

FIG. 23 is a diagram illustrating an EPS update type information elementaccording to an embodiment of the present invention.

Referring to FIG. 23, the EPS update type IE has a length of one octet,4 bits (i.e., bit 5 to bit 8) from the most significant bit (MSB)(alternatively, the left-most bit) Indicates an EPS update typeinformation element identifier (IEI), the next 1 bit (i.e., bit 4)indicates the “Active” flag, the next 1 bit (i.e., bit 3) indicates aNEW Flag, and the next two bits (i.e., bit 2 and bit 1) indicate EPSupdate type values.

TABLE 5 EPS update type value (octet 1, bits 1 to 3) Bits 2 1 0 0 TAupdating 0 1 Combined TA/LA (Location Area) updating 1 0 Combined TA/LAupdating with IMSI attachment 1 1 Periodic updating Additionalindication setting (octet 1, bit 3) Bit 3 0 Immediately connectionrelease after completion of the procedure (i.e., release connectionimmediately after procedure completion of TAU, etc. like the operationin the related art) 1 Presence of MO data (MO data over NAS) throughNAS/Connection retention/No DRB setup (do not release immediately aftercompletion of TAU, etc.) “Active” flag (octet 1, bit 4) Bit 4 0 Nobearer establishment request 1 Bearer establishment request

Option 3) Definition and use of new IE

The transmission of the tracking area update request to the network bythe UE is shown in Table 6 below.

Table 6 illustrates TRACKING AREA UPDATE REQUEST message contents.

TABLE 6 Information element identifier (IEI) Information elementType/Reference Presence Format Length Protocol Protocol discriminator MV 1/2 discriminator TS 24.301 9.2 Security header type Security headertype M V 1/2 TS 24.301 9.3.1 Tracking area update Message type M V 1request message TS 24.301 9.8 identity EPS update type EPS update type MV 1/2 TS 24.301 9.9.3.14 NAS key set NAS key set identifier M V 1/2identifier TS 24.301 9.9.3.21 Old GUTI EPS mobile identity M LV 12 TS24.301 9.9.3.12 B- Non-current native NAS key set identifier O TV 1 NASkey set TS 24.301 9.9.3.21 identifier  8- GPRS ciphering key Cipheringkey O TV 1 sequence number sequence number TS 24.301 9.9.3.4a 19 OldP-TMSI signature P-TMSI signature O TV 4 TS 24.301 9.9.3.26 50Additional GUTI EPS mobile identity O TLV 13  TS 24.301 9.9.3.12 55NonceUE Nonce O TV 5 TS 24.301 9.9.3.25 58 UE network UE networkcapability O TLV 4-15 capability TS 24.301 9.9.3.34 52 Last visitedregistered Tracking area identity O TV 6 TAI TS 24.301 9.9.3.32  5C DRXparameter DRX parameter O TV 3 TS 24.301 9.9.3.8 A- UE radio capabilityUE radio capability O TV 1 information update information update neededneeded TS 24.301 9.9.3.35 57 EPS bearer context EPS bearer context O TLV4 status status TS 24.301 9.9.2.1 31 MS network MS network O TLV 4-10capability capability TS 24.301 9.9.3.20 13 Old location area Locationarea O TV 6 identification identification TS 24.301 9.9.2.2  9- TMSIstatus TMSI status O TV 1 TS 24.301 9.9.3.31 11 Mobile station Mobilestation O TLV 5 classmark 2 classmark 2 TS 24.301 9.9.2.4 20 Mobilestation Mobile station O TLV 2-34 classmark 3 classmark 3 9.9.2.5 40Supported Codecs Supported Codec List O TLV 5-n  TS 24.301 9.9.2.10 F-Additional update Additional update O TV 1 type type TS 24.301 9.9.3.0B 5D Voice domain Voice domain O TLV 3 preference and UE's preference andUE's usage setting usage setting TS 24.301 9.9.3.44 E- Old GUTI typeGUTI type TS 24.301 O TV 1 9.9.3.45 D- Device properties Deviceproperties O TV 1 TS 24.301 9.9.2.0A C- MS network feature MS networkfeature O TV 1 support support TS 24.301 9.9.3.20A 10 TMSI based networkNetwork resource O TLV 4 resource identifier identifier container (NRI)container TS 24.301 9.9.3.24A  6A T3324 value GPRS timer 2 O TLV 3 TS24.301 9.9.3.16  5E T3412 extended value GPRS timer 3 O TLV 3 TS 24.3019.9.3.16B  6E Extended DRX Extended DRX O TLV 3 parameters parameters TS24.301 9.9.3.46 XX New Indication for New Indication for O TV 1Connection release Connection release TS 24.301 9.9.3.XX

New indication for connection release IE is coded as illustrated in FIG.24 and Table 7 below.

FIG. 24 is a diagram illustrating a new indication information elementfor connection release according to an embodiment of the presentinvention.

Referring to FIG. 24, a new indication IE for connection release has alength of 1 octet and 4 bits (i.e., 5 to 8 bits) from the mostsignificant bit (MSB) (or left-most bit)) represent an additional updatetype information element identifier (IEI), the next 3 bits (i.e., bits4, 3, and 2) represent spare bits, and the next one bit (i.e., bit 1)represents a new flag.

Table 7 shows a New Indication for Connection release IE.

TABLE 7 Additional indication setting (octet 1, bit 1) Bits 1 0connection release after procedure completion (releasing connectionimmediately after completion of the TAU, etc. like the operation in therelated art) 1 MO data over NAS exists/connection is maintained/DRB isnot set up (not immediately released immediately after termination ofthe TAU, etc.)

Overview of Devices to which the Present Invention can be Applied

FIG. 25 illustrates a block diagram of a communication device accordingto one embodiment of the present invention.

With reference to FIG. 25, a wireless communication system comprises anetwork node 2510 and a plurality of UEs 2520.

A network node 2510 comprises a processor 2511, memory 2512, andcommunication module 2513. The processor 2511 implements proposedfunctions, processes and/or methods proposed through FIG. 1 to FIG. 24.The processor 2511 can implement layers of wired/wireless interfaceprotocol. The memory 2512, being connected to the processor 2511, storesvarious types of information for driving the processor 2511. Thecommunication module 2513, being connected to the processor 2511,transmits and/or receives wired/wireless signals. Examples of thenetwork node 2510 include an eNB, MME, HSS, SGW, PGW, application serverand so on. In particular, in case the network node 2510 is an eNB, thecommunication module 2513 can include a Radio Frequency (RF) unit fortransmitting/receiving a radio signal.

The UE 2520 comprises a processor 2521, memory 2522, and communicationmodule (or RF unit) 2523. The processor 2521 implements proposedfunctions, processes and/or methods proposed through FIG. 1 to FIG. 24.The processor 2521 can implement layers of wired/wireless interfaceprotocol. The memory 2522, being connected to the processor 2521, storesvarious types of information for driving the processor 2521. Thecommunication module 2523, being connected to the processor 2521,transmits and/or receives wired/wireless signals.

The memory 2512, 2522 can be installed inside or outside the processor2511, 2521 and can be connected to the processor 2511, 2521 throughvarious well-known means. Also, the network node 2510 (in the case of aneNB) and/or the UE 2520 can have a single antenna or multiple antennas.

FIG. 26 illustrates a block diagram of a wireless communicationapparatus according to an embodiment of the present invention.

Particularly, in FIG. 26, the UE described above FIG. 25 will beexemplified in more detail.

Referring to FIG. 26, the UE includes a processor (or digital signalprocessor) 2610, RF module (RF unit) 2635, power management module 2605,antenna 2640, battery 2655, display 2615, keypad 2620, memory 2630,Subscriber Identification Module (SIM) card 2625 (which may beoptional), speaker 2645 and microphone 2650. The UE may include a singleantenna or multiple antennas.

The processor 2610 may be configured to implement the functions,procedures and/or methods proposed by the present invention as describedin FIG. 1-24. Layers of a wireless interface protocol may be implementedby the processor 2610.

The memory 2630 is connected to the processor 2610 and storesinformation related to operations of the processor 2610. The memory 2630may be located inside or outside the processor 2610 and may be connectedto the processors 2610 through various well-known means.

A user enters instructional information, such as a telephone number, forexample, by pushing the buttons of a keypad 2620 or by voice activationusing the microphone 2650. The microprocessor 2610 receives andprocesses the instructional information to perform the appropriatefunction, such as to dial the telephone number. Operational data may beretrieved from the SIM card 2625 or the memory module 2630 to performthe function. Furthermore, the processor 2610 may display theinstructional and operational information on the display 2615 for theuser's reference and convenience.

The RF module 2635 is connected to the processor 2610, transmits and/orreceives an RF signal. The processor 2610 issues instructionalinformation to the RF module 2635, to initiate communication, forexample, transmits radio signals comprising voice communication data.The RF module 2635 comprises a receiver and a transmitter to receive andtransmit radio signals. An antenna 2640 facilitates the transmission andreception of radio signals. Upon receiving radio signals, the RF module2635 may forward and convert the signals to baseband frequency forprocessing by the processor 2610. The processed signals would betransformed into audible or readable information outputted via thespeaker 2645.

The aforementioned embodiments are achieved by combination of structuralelements and features of the present invention in a predeterminedmanner. Each of the structural elements or features should be consideredselectively unless specified separately. Each of the structural elementsor features may be carried out without being combined with otherstructural elements or features. Also, some structural elements and/orfeatures may be combined with one another to constitute the embodimentsof the present invention. The order of operations described in theembodiments of the present invention may be changed. Some structuralelements or features of one embodiment may be included in anotherembodiment, or may be replaced with corresponding structural elements orfeatures of another embodiment. Moreover, it will be apparent that someclaims referring to specific claims may be combined with another claimsreferring to the other claims other than the specific claims toconstitute the embodiment or add new claims by means of amendment afterthe application is filed.

The embodiments of the present invention may be achieved by variousmeans, for example, hardware, firmware, software, or a combinationthereof. In a hardware configuration, the methods according to theembodiments of the present invention may be achieved by one or moreApplication Specific Integrated Circuits (ASICs), Digital SignalProcessors (DSPs), Digital Signal Processing Devices (DSPDs),Programmable Logic Devices (PLDs), Field Programmable Gate Arrays(FPGAs), processors, controllers, microcontrollers, microprocessors,etc.

In a firmware or software configuration, the embodiments of the presentinvention may be implemented in the form of a module, a procedure, afunction, etc. Software code may be stored in a memory unit and executedby a processor. The memory unit may be located at the interior orexterior of the processor and may transmit data to and receive data fromthe processor via various known means.

It will be apparent to those skilled in the art that variousmodifications and variations can be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

INDUSTRIAL APPLICABILITY

The present invention is applied to a 3GPP LTE/LTE-A system is primarilydescribed, but can be applied to various wireless communication systemsin addition to the 3GPP LTE/LTE-A system.

The invention claimed is:
 1. A method for performing, by a userequipment (UE), a tracking area update (TAU) procedure in a wirelesscommunication system, the method comprising: transmitting a TAU requestmessage to a mobility management entity (MME); receiving a TAU acceptmessage from the MME; and starting a predetermined timer based on afirst active flag in the TAU request message not being set, wherein whenthe UE uses signaling optimization to enable the delivery of user datathrough a control plane via the MME, and the UE does not have pendinguser data to be transmitted through a user plane and has pending userdata to be transmitted through the control plane via the MME, then thefirst active flag is set in the TAU request message.
 2. The method ofclaim 1, wherein the first active flag is used for a request formaintaining a non-access stratum (NAS) signaling connection between theUE and the MME after completion of the TAU procedure.
 3. The method ofclaim 1, wherein the first active flag is included in an additionalupdate type information element for providing additional informationregarding a type of a request for the TAU procedure in the TAU requestmessage.
 4. The method of claim 3, wherein when a value of the firstactive flag is ‘0’, the non-access stratum (NAS) signaling connectionbetween the UE and the MME is not maintained after the completion of theTAU procedure.
 5. The method of claim 3, wherein when a value of thefirst active flag is ‘1’, the non-access stratum (NAS) signalingconnection between the UE and the MME is maintained after the completionof the TAU procedure.
 6. The method of claim 1, wherein based the timerexpiring, the non-access stratum (NAS) signaling connection between theUE and the MME is released by the UE.
 7. The method of claim 1, whereinwhen the UE does not successfully perform the TAU procedure and amobility management (MM) back-off timer is driven, the UE transmits theTAU request after receiving a paging.
 8. The method of claim 1, whereinwhen the UE has the pending user data through the user plane, a secondactive flag is set in the TAU request message.
 9. A user equipment (UE)performing a tracking area update (TAU) procedure in a wirelesscommunication system, the user equipment comprising: a transceiver; atleast one processor; and at least one computer memory operableconnectable to the at least one processor and storing instructions that,when executed by the at least one processor, perform operationscomprising: transmitting, via the transceiver, a TAU request message toa mobility management entity (MME); receiving, via the transceiver, aTAU accept message from the MME; and starting a predetermined timerbased on a first active flag in the TAU request message not being set,wherein when the UE uses signaling optimization to enable the deliveryof user data through a control plane via the MME, and the UE does nothave pending user data to be transmitted through a user plane and haspending user data to be transmitted through the control plane via theMME, then the first active flag is set in the TAU request message. 10.The user equipment of claim 9, wherein the first active flag is used fora request for maintaining a non-access stratum (NAS) signalingconnection between the UE and the MME after completion of the TAUprocedure.
 11. The user equipment of claim 9, wherein the first activeflag is included in an additional update type information element forproviding additional information regarding a type of a request for theTAU procedure in the TAU request message.
 12. The user equipment ofclaim 11, wherein when a value of the first active flag is ‘0’, thenon-access stratum (NAS) signaling connection between the UE and the MMEis not maintained after the completion of the TAU procedure.
 13. Theuser equipment of claim 11, wherein when a value of the first activeflag is ‘1’, the non-access stratum (NAS) signaling connection betweenthe UE and the MME is maintained after the completion of the TAUprocedure.
 14. The user equipment of claim 9, wherein based the timerexpiring, the non-access stratum (NAS) signaling connection between theUE and the MME is released by the UE.
 15. The user equipment of claim 9,wherein when the UE does not successfully perform the TAU procedure anda mobility management (MM) back-off timer is driven, the UE transmitsthe TAU request after receiving a paging.
 16. The user equipment ofclaim 9, wherein when the UE has the pending user data through the userplane, a second active flag is set in the TAU request message.